A post on Loosely Coupled offers a model of web services layers from 'routers' (the messaging layer where we tend to focus at the moment) to 'decisioneers' where business requirements are fed into the architecture.
Attention is starting to shift from the lower levels of SOA -- where people argue about ESB, SOAP vs REST, security and other message-level minutiae -- up to layers that merit a lot more thought than they've so far enjoyed in SOA debate. I'm talking here about things like registry, policy, governance, semantics and -- most important of them all -- business process management. [LCblog | Missing layers of SOA | Mar 3rd 2005 4:10pm]I liked the note about registration.
Registries. This is where everything gets recorded. Some people might class it as two layers; there's certainly a lot going on here. The recording includes identity information as well as policy settings. There may be taxonomies here too. The common factor across all these functions is that we're talking about a trusted system of record, which is why we use the word 'registry', with its implication of some kind of formal [LCblog | Missing layers of SOA | Mar 3rd 2005 4:10pm]As we build more networked library services, we run into more need for registries. Think of the knowledge-bases we are developing.
Registries and their administration (here included in another layer 'governers') are becoming more important for us.