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.
It is four months since the SOA manifesto was announced; InfoQ interviewed the original author’s and in some cases pulled in their comments on the manifesto from the web to get a broad understanding of the manifesto, as well as provide insight into the goals of the participants, individually and as a whole, and provide transparency to the mechanics involved in putting together such an initiative.
Service Oriented Architecture (SOA) has been widely accepted as an approach that facilitates business agility by aligning IT with business. In this article, Rathina Dhandapani, highlights key best practices in an SOA initiative to identify, validate and verify service inventory content well before implementation.
Reuse can be hard, especially in a large organization. Vijay Narayanan offers 10 practical tips to assure effective reuse of software components. 4
This article from Atlassian, discusses four aspects of automated builds and continuous integration: communication flow, effective builds, code quality, and automated deployment. 4
Pierre Bonnet argues that information systems are too opaque and not agile enough. He claims this is the main reason why "healthy" companies can collapse within months as they take on too much risk. 5
This article proposes a new Message Type Architecture to help manage the message formats in a SOA. The approach promotes reuse and helps aligning the Data and SOA governance processes. 28
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
The hardest thing about a successful adoption of SOA is not the technology, but rather, the culture change. Todd Biske offers his perspective on using Governance to drive culture change. 1
This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring. 5
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. 3
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