Architect Consultant blog

There were probably already hundreds of discussions about versioning XML schemas and WSDL documents. This Blog considers the strategy described in Thomas Erl's "Web Service Contract Design and Versioning for SOA". How would you use these practices within a CDM? This Blog considers some options you have when developing XML Schemas out of you logical CDM. Consider a small CDM in which the following model is used. LegalEntity <-- NaturalPerson <-- Employee                   <-- NonNaturalPerson Namespaces For these entities you have some possibilities to use namespaces: 1) A group of Entities share the same namespace Example: http://www.blog/organisation/v1 2) Each Entity gets its own namespace Example: http://www.blog/organisation/legalentity/v1 http://www.blog/organisation/naturalperson/v1 The advantages of option 1 are Only 1 namespace needed, namespaces are hell as we all...

This week I had a discussion about a federated ESB and functional domains. It is widespread known that a CDM within an enterprise is hard to achieve and that's why the enterprise is divided in functional domains. However a common mistake often made, is that this division is done on a 1-by-1 mapping to the organisational divisions. Reasons I hear: * "Then we can make this department responsible for those processes" * ".. and those department is responsible for those systems/applications" This again is the silo-based concept of thinking. This division is furthermore also visible in the division of domains within the IT landscape (federated ESBs). But if there is one variable that often changes it will be the organisation. Also most processes will span multiple areas and it is very difficlut to keep that in one domain. However the business of the organisation and the functions the business must offer is more stable. So divide your SOA landscape on a functional basi...

This is a presentation I made about "why to use CDM?" and "where transformation can be done". It is in Dutch, please feel free to comment on it !

This item is about a CDM a.k.a CMM (Common Message Model) on the Bus, why is it wise and how can it be done. First of all when you face a integration challenge the systems to be integrated are heterogeneous and use different data models (syntactically and semantically). So the data needs to be mapped from requester data to provider data. 1) Direct mapping, this results in n * m mappings (n=#requestors, m=#providers) and is very costly when a new provider or requester is added. 2) CDM, this results in n + m mappings A CDM gives you: Message consistency Message maintainability A CDM is a set of data representing the business entities used in all messages on the Bus. This does not mean that each provider or requestor uses the same set of messages but that the messages are all based on the same types. Possible implementations for CDM on ESB Option 1: ESB translates The requestor and provider keep their own models Only CDM is used on ESB Existing services do not have to be changed (especial...