--- In [email protected], Michael Poulin <m3pou...@...> wrote: > > Honestly, I do not see a pattern in here. This is rather a snapshot of > project planning and management guidelines.
It does seem a bit strange to call this a pattern. I guess it could be considered an IT management or governance pattern, one which allows and even encourages independent SOA initiatives within an enterprise. > > At the same time, I do not see here any recommendations on how to make a > domain inventory really working without having corresponding Business working > in services for the same domain. If Business does not support and recognise > such inventory, it becomes the old dead SOA-in-IT... > I agree to some extent, but old and dead-style SOA is not prohibited by this "pattern". In fact it doesn't prescribe the style or quality of the SOA, and each domain could decide that on its own. But the hope would be that if the domain is of manageable size, SOA has a better chance of being done right. It seems to me this is what most companies have been doing for SOA, probably starting at a group or department level, then recognizing the potential to bubble it up to at least a domain level. It's a recognition that big bang SOA rarely could work, and it proposes the next best thing: apply SOA to as broad a domain that will work. Makes a lot of sense to me, even if we can't agree to call this a pattern. -Kirstan
