There are many opportunities to begin breaking down your monolithic applications one feature at a time, but other parts of your legacy portfolio are operating just fine and aren’t going anywhere. New microservices and legacy systems have to interoperate—and that's no easy task. One option is to rebuild everything, but that's costly, risky, and time-consuming. You could also integrate new services and legacy systems with APIs, but there are challenges there, too. Using a code-scanning tool to convert from, say, Cobol to Java, may just move the mess you had in Cobol to Java. At the end of the day, some of your legacy services are doing just fine, but to support new customer-facing capabilities and channels, you need to easily access their functionality and data.
In this session, you'll learn:
why common approaches to modernizations are costly, risky, and can fail to achieve the desired outcome of making code simpler and easier to maintain
how an event-driven architecture can be used to connect microservices to legacy systems
how to handle the nuances of an event-driven architecture solution that will need to be managed, such as how to handle PII
why events from legacy systems are not always easy to consume by new microservices, and what pattern can be used to address this