If you've been following me, you know I'm all about the data when considering SOA. Services are indeed important, however the understanding, management, and use of data is something that needs to be the foundation of your SOA, as with any architecture. As I always say, you need a semantic or data-level understanding of your problem domain, then services, then processes. Truth-be-told many neglect the data, and d If you’ve been following me, you know I’m all about the data when considering SOA. Services are indeed important, however the understanding, management, and use of data is something that needs to be the foundation of your SOA, as with any architecture. As I always say, you need a semantic or data-level understanding of your problem domain, then services, then processes. Truth-be-told many neglect the data, and data connectivity, when designing and building their SOA. This mistake typically causes project failure, or even worse ineffective SOAs that really just add to the complexity of the core architecture. That’s not good. So, I’m out again preaching to masses about data and SOA, including these three architectural tutorials I’m doing this week in St. Luis (today), next week in Toronto, and the following week in Irvine. All the info is here, and the price is right. Software Development