Getting Microservices and Legacy to Play Nicely Together with Event-Driven Architectures
2 likes499 views
The document discusses techniques for modernizing legacy systems, including digital decoupling. Digital decoupling aims to isolate legacy systems to break the cycle of increasing costs when adding features. It unlocks constrained legacy data and delivers new business value on a modern cloud architecture. This allows replacing the core systems over time while continuously delivering value. The key techniques discussed are using microservices, change data capture, event-driven architectures, and domain-driven design to begin digitally decoupling legacy systems.
Getting Microservices and Legacy to Play Nicely Together with Event-Driven Architectures
- 1. Getting Microservices and Legacy to Play Nicely Together with Event-Driven Architectures October 9, 2019 Austin Convention Center
- 2. Copyright © 2019 Accenture. All rights reserved. Why does modernization often cost so much? 2
- 3. Copyright © 2019 Accenture. All rights reserved. TOO MUCH TECHNOLOGY DEBT Why does modernization often cost so much? 3
- 4. Copyright © 2019 Accenture. All rights reserved. The legacy paradox Technical debt in our legacy systems severely limits our IT function’s ability to be innovative Technical debt in our legacy systems increases our IT Costs The Good, … The Bad … and, The Ugly Source: Accenture Research Digital Decoupling Survey, July 2018 Our legacy systems contain trapped value that can be used for innovation 4
- 5. Copyright © 2019 Accenture. All rights reserved. What are some techniques for modernization? 5
- 6. Copyright © 2019 Accenture. All rights reserved. We could use a code translation tool And transmogrify it. Code Generation Tools 6
- 7. Copyright © 2019 Accenture. All rights reserved. We could build a new system to replace it. 7
- 8. Copyright © 2019 Accenture. All rights reserved. We could containerize it. 8
- 9. Copyright © 2019 Accenture. All rights reserved. We could use microservices in the cloud… Micro- service A Micro- service B 9
- 10. Copyright © 2019 Accenture. All rights reserved. …and “just” replace pieces of it Micro- service A New API Layer Call APIs to Synchronize Micro- service B Retire 10
- 11. Copyright © 2019 Accenture. All rights reserved. DIGITAL DECOUPLING Change the business… while running the business 11
- 12. Copyright © 2019 Accenture. All rights reserved. We can have old and new, at the same time Micro-serv ice A New API Layer Call APIs to Synchronize Pub-Sub to Synchronize Change Data Capture Micro-serv ice B 12
- 13. Copyright © 2019 Accenture. All rights reserved. Pivoting to new while leveraging the good in Legacy Fundamentally, Digital Decoupling is a new methodology to: 1. Isolate legacy systems so as to break the cycle of multiplicative cost when adding or integrating features. 2. Unlock the data that has been constrained by the legacy systems and make it accessible. 3. Deliver new business value on top of a modern, cloud native architecture capable of delivering new products quickly. 4. Hollow out and replace the core gradually over time, ending with new systems within similar timelines to the old transformations, but with far more value delivered along the way. 13
- 14. Copyright © 2019 Accenture. All rights reserved. Domain APIs 14 Legacy / package / SaaS Domain Microservice Engagement Channels Event Hub Legacy / Package / SaaS New Decoupling Components Channels Legacy / Package / SaaS System REST Endpoints Data flow Event Consumer Domain DB Event Producer Web Service(s) Event Consumer Event Consumer Specialized View REST Endpoints Event Consumer DB / In-Memor y Data Lake Reporting & Insights API ViewViewData Stores Event Consumer Legacy DB Transformer Event Consumer / Producer CDC Event Consumer Insights Engagement Service DB / In-Memor y Engagement APIs Digital Decoupling Pattern
- 15. Copyright © 2019 Accenture. All rights reserved. Change Data Capture (CDC) Event-Driven Architecture / Event Streaming Microservices 15 The Building Blocks
- 16. Copyright © 2019 Accenture. All rights reserved. Begin the journey to digital decoupling 1. Use domain driven design and build microservices 2. Build a proof of architecture 3. Performance test it 4. Keep it simple 5. Be mindful of where the data is