Articles
Contract-Driven Development – a Real-World Adoption Journey
The story of how a large financial services company adopted contract-driven development. Covering the situation on the ground before adoption and initial skepticism, and how we were able to influence change by demonstrating value and eventually getting people to collaborate over API specifications.
[Contract Driven Development – Post 2] Integration Hell
Integration Tests require the actual components/microservices to be deployed to a common environment. Because of this integration tests are able to verify the connections between these microservices which was never verified until this point since ...
Read Article
[Contract Driven Development – Post 1] – The trouble with API mocks and stubs
Over the last 6-7 years, I’ve studied several microservices architecture transformations. What I’ve realised is a lot of them are not bearing the returns the stakeholders were expecting. Many organisations were expecting that they would ...
Read Article
Microservices Integration Done Right Using Contract-Driven Development
Contract Driven Development helps us leverage API specifications as executable contracts using Specmatic to shift left the identification of compatibility issues thereby eliminating / reducing the need for integration tests.
Read Article