There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.
Today we introduce the book “Web Service Contract Design and Versioning for SOA” by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, L. Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley. More exactly, chapters 20, 21, and 22 of the book addressing the issues related to service contract versioning.
Improving the Performance of Automatic Configuration Management Processes by Encouraging Human Intervention
This case study focuses on how bwin was able to improve efficiency by including human intervention as a major part of an automatic configuration management system.
This article shows how recommended contract versioning design policies relate to a SOA Maturity Model. The goal is to provide a roadmap for achieving versioning and composability.
Kjell-Sverre and Jean-Jacques revisit the concept of compatible contract based on XML, XML Schema and WSDL extensibility to foster service reuse and complement Governance. 29
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar. 29
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier. 1
When several teams work in the same codebase there's always risk of chaos. Henrik's "Scrum & XP from the Trenches" approach is a simple way to ensure clean, releasable code with every iteration. 19