Building on his earlier article, “Distributed Version Control Systems in the Enterprise”, Pablo Santos discusses his company’s product: PlasticSCM. While other DVCS systems were designed for the needs of the Linux open source community, PlasticSCM addresses the problems facing enterprise software developers, especially those using .NET.
Matt Callanan has been pushing the boundaries of Agile software development for over six years and most recently he extended that journey to DevOps. He recently shared his experiences in a talk at the Agile Development Practices West conference entitled "Lessons From A DevOps Journey". InfoQ caught up with Matt prior to the conference to find out more about his experiences in DevOps.
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. 5
Today we introduce the book “Web Service Contract Design and Versioning for SOA”, more exactly, chapters 20, 21, and 22 of the book addressing the issues related to service contract versioning. 11
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