Wesley Reisz talks to Daniel Bryant on moving from monoliths to micro-services, covering bounded contexts, when to break up micro-services, event storming, practices like observability and tracing, and more.
Why listen to this podcast:
- Migrating a monolith to micro-services is best done by breaking off a valuable but not critical part first.
- Designing a greenfield application as micro-services requires a strong understanding of the domain.
- When a request enters the system, it needs to be tagged with a correlation id that flows down to all fan-out service requests.
- Observability and metrics are essential parts to include when moving micro-services to production.
- A service mesh allows you to scale services and permit binary transports without losing observability.
More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2pFYBiT
You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pFYBiT