Distributed systems are hard. Building a microservices architecture that supports evolutionary changes without causing massive problems? Especially hard. In this podcast, we grabbed Pivotal employees Oliver Gierke, Kenny Bastani, and Andrew Clay Shafer to discuss microservices design and evolution. We chatted about decomposing monolithic systems, limiting coupling and communication between services, defining contracts that can be shared with consumers to “test” the service, and various approaches for versioning a service. While we didn’t experience a magical epiphany, we did uncover some important considerations for teams that are heading down a microservices path.
- Visit https://blog.pivotal.io/pivotal-conversations for show notes and other episodes.
- Download the episode directly, check us out in SoundCloud, subscribe to the feed directly, or in iTunes to have it automatically downloaded for you.
- Twitter: @cote, @rseroter, @kennybastani, @olivergierke, and @littleidea.
- Feedback: firstname.lastname@example.org
Contracts & friends
- “Consumer-Driven Contracts: A Service Evolution Pattern.”
- Oliver’s blog post, “Evolving Distributed Systems.”
- “Understanding the Costs of Versioning an API (or a Service).”
- “Systems that Run Forever Self-heal and Scale.”
About the AuthorMore Content by Coté