on
Contract-Driven Development - Key takeaways from a Real-World Adoption Journey
Key Takeaways: Contract-Driven Adoption
I had the privilege of publishing an in-depth article on InfoQ about the real-world adoption journey of Contract-Driven Development (CDD). The full article covers the challenges, the collaboration models, and the data used for organizational change.
Below are the key takeaways excerpted directly from that article.
-
Contract-driven development (CDD) can help with microservices integration but needs a new collaboration model among stakeholders.
-
CDD involves writing and storing API specifications before building applications, which is different from usual practices and may take time to adopt.
-
CDD builds on and contributes to a strong test pyramid which requires changes to test composition, strategy and application architecture to improve component testability.
-
Start the CDD adoption journey with a few teams first to show its value and identify the necessary changes to your way of working before expanding it to others.
-
Use the learnings and data from initial proof of concept to persuade leadership and others to help drive large scale adoption through smooth onboarding experience with contextualized playbooks and utilities for CDD.
Read the Full Article
Read the full article on InfoQ: Contract-Driven Adoption
This is an excerpt from an article written by Hari Krishnan and published on InfoQ about contract-driven development adoption. All key takeaways are excerpted from the original article. For the complete context and detailed insights, please read the full article on InfoQ.