December 16, 2019

261 words 2 mins read

Moving to microservices: Using domain-driven design to break down the monolith

Moving to microservices: Using domain-driven design to break down the monolith

Agile practices and techniques like continuous delivery are all about being able to react to changes rapidly, but putting them into practice when you have a big monolith application can be difficult. Microservices offer one solution. Maria Gomez shows you how to move from a monolith to microservices by applying domain-driven design principles.

Talk Title Moving to microservices: Using domain-driven design to break down the monolith
Speakers Maria Gomez (BCG Digital Ventures)
Conference O’Reilly Software Architecture Conference
Conf Tag Engineering the Future of Software
Location New York, New York
Date February 4-6, 2019
URL Talk Page
Slides Talk Slides
Video

Agile practices and techniques like continuous delivery and evolutionary architecture are all about being able to react to changes rapidly. However, putting them into practice when you have a big legacy monolith application can be a difficult job, so recently the industry has come out with different ideas to solve this problem. Microservices, pushed by companies like Netflix or Amazon, are the latest solution to this problem. Having an architecture based on services offers many advantages (like scalability and technical flexibility), but it comes with upfront costs and complexity that few companies are in a position to pay. Maria Gomez explores the prerequisites for moving into a microservices architecture and shares tips on how to achieve them. You’ll learn how to assess whether a microservice architecture is right for your organization; establish prerequisites for moving to microservices, including testing, automation, and continuous delivery; identify and decouple contexts using domain-driven design and refactoring techniques; and extract microservices from a monolith. Topics include:

comments powered by Disqus