Christopher Goldsbury explores some "bad attitudes" of Agility - assertions about management, documentation, testing, teams, and schedules that are commonly encountered, but contrary to reality. These bad attitudes find refuge and justification in Agile despite the fact they are false. Addressing these viewpoints before they, potentially, darken a good movement is essential.
This paper looks at various error handling considerations associated with design of re-usable services and provides an outline of what error handling considerations apply during SOA analysis and design phases and also describes some best practices into designing these considerations to ensure that services are designed and implemented in all its completeness.
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 to get insight into the motivations and the process behind the initiative. 9
In this article, Rathina Dhandapani, highlights key best practices in an SOA initiative to identify, validate and verify service inventory content well before implementation. 1
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