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

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
Case Study: How Pivotal Network Does Zero Downtime Deployment on Cloud Foundry
Case Study: How Pivotal Network Does Zero Downtime Deployment on Cloud Foundry

At the end of last quarter, Pivotal Network (the platform for evaluating Pivotal Software) came out of a th...

Next
Elisabeth Hendrickson on Using PaaS for Continuous Delivery at the Cloud Foundry Summit
Elisabeth Hendrickson on Using PaaS for Continuous Delivery at the Cloud Foundry Summit

During a technical breakout session at the Cloud Foundry Summit 2014, Elisabeth Hendrickson, director of qu...

Return to Home