Summary of The journey from monolith to microservices – Mike Gehard | The Lead Developer UK 2016

00:00:00 - 00:25:00

In this video, Mike Gehard discusses the journey from monolith to microservices. He discusses the benefits of moving to microservices, as well as the upfront costs associated with making the switch. He also provides an example of how microservices can be used to change an application based on the needs of the application domain.

• 00:00:00 In his talk "The journey from monolith to microservices – Mike Gehard | The Lead Developer UK 2016," Mike Gehard discusses how the pressures of modern software development lead to the migration from monoliths to microservices. He goes on to explain how the app continuum concept formalizes this migration path, and how a client project can be a good way to try it out.
• 00:05:00 The speaker discusses how Netflix and Hulu developed scalable microservices and how this created a dangerous situation due to the lack of comprehensive current API tests. They recommend starting with well-structured monoliths before moving on to microservices.
• 00:10:00 The video discusses the journey from monolith to microservices, and how to organize an application for better testing and development. It also discusses the concept of bounded context and how to break it out into multiple components.
• 00:15:00 Mike Gehard describes the journey from monoliths to microservices, highlighting the benefits of moving to microservices while avoiding the overhead of microservices. He also provides an example of how to move a component from one application to another across a network.
• 00:20:00 The speaker discusses their journey from monolith to microservices, and how they've incurred two new costs - service discovery and partition tolerance. They also mention how they are monitoring their microservices to ensure they remain running and responsive.
• 00:25:00 In this video, Mike Gehard discusses his journey from monolith to microservices. He notes that, in order to move from monolith to microservices, he had to pay upfront costs (e.g. in terms of development time and costs associated with changing communication interfaces). He also discusses how microservices can be easily changed based on the needs of the application domain, and how Martin Fowler is a good resource for learning about microservices.