Inter-Service Communication, Consumer-Driven Contract Testing, and Service Versioning (Ep. 39)

November 3, 2016 Coté


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.

Show Notes

Contracts & friends

About the Author

Biography

Previous
Episode 36: A false choice: systems of record vs. systems of engagement (Ep. 49)
Episode 36: A false choice: systems of record vs. systems of engagement (Ep. 49)

What's the best way to categorize and prioritize your IT projects? Splitting them up between systems of rec...

Next
Pivotal Cloud Foundry 1.8 with Jared Ruckle (Ep. 35)
Pivotal Cloud Foundry 1.8 with Jared Ruckle (Ep. 35)

This week, we talk with Jared Ruckle about the new Pivotal Cloud Foundry 1.8 release, delving into securi...