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

More Content by Coté
Previous
What is Happening to the Data Warehouse Market? (Ep. 8)
What is Happening to the Data Warehouse Market? (Ep. 8)

In this episode of Pivotal Insights, host Jeff Kelly speaks to a group of Pivotal data engineering leaders...

Next
To Avoid Getting Caught In The Developer Skills Gap, Do This.
To Avoid Getting Caught In The Developer Skills Gap, Do This.

The Global Perception Study by the Cloud Foundry Foundation shows that the majority (>60%) of companies wan...

Enter curious. Exit smarter.

Learn More