Pierre Bonnet, CTO of Orchestra Networks, argues that information systems are too opaque and not agile enough. He claims this is the main reason why "healthy" multinationals can collapse within months as they take on too much risk. He suggests that information systems be rated on how they manage master data, business rules and business processes.
This article proposes a new Message Type Architecture based on two DSLs to help manage the message formats in a SOA. The approach promotes reuse via the Enterprise Data Model referenced in message type definitions. It also helps aligning the Data and SOA governance processes.
Kjell-Sverre and Jean-Jacques revisit the principles of contract design focusing on the concept of compatible contract based on XML, XML Schema and WSDL extensibility to foster service reuse and complement Governance. The article includes a novel approach to manage message types in relation to an enterprise data model.
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
Many organizations loves best practices and thinks it helps. In this article, Dan North shows how they can not only fail to help, but even have a severe negative impact on your top performers. 16
In this article, Gernot Starke introduces SOA Governance, how it relates to overall Corporate Governance and IT Governance, and how it should be applied both at design-time and at runtime. 4
Kent Beck's new book, Implementation Patterns, gives a coherent view of how to write code people can understand that serves human as well as economic needs. 2
In this article, Stefan Tilkov proposes 10 principles to serve as a basis for SOA discussions, focusing on abstract concepts that are independent from any particular vendor framework. 6