Saturday, November 22, 2008

It's All About the Data...


image This article from Bill Snyder shows that in many SOA projects the data and its structure does not get the attention that it should.
For a working 360° view of a customer - something that Amdocs is propagating for years now - many data silos must be integrated and made accessible within an SOA. It is not only about (business) processes and services, the data is as important, especially when it comes to CRM.
In a CRM 2.0 strategy, the data and its availability is crucial. Customers expect all data (and services) to be available whenever and wherever they need it. There is no real personal treatment of customers without a 360° view of their data.
How can this be achieved?
One possible solution is a shared information datamodel (SID) or an existing standard datamodel like TMFs structure. This can either be used by all SOA services or be mapped to them individually (legacy apps).


Technorati-Tags: ,,,

Friday, November 7, 2008

SOA 2.0 and SOA Governance

925147_linked_hands While I am reading through articles around SOA Governance and Registry / Repository, I keep thinking that this might be the first and most important part for collaboration in an SOA.

A Registry / Repository (I love the Repistry expression) is THE central place for all information around an SOA architecture. This is the place where developers need to communicate and collaborate amongst each other and with designers, architects and even customers / partners.

Wouldn't this be the most valuable place for Web 2.0 techniques within an SOA implementation?

Isn't it crucial to engage all participating parties to share information and leverage the tools that the Web 2.0 offers?

Monday, October 20, 2008

SOA 1.0 + EDA = SOA 2.0 ??

It looks like Gartner has a different interpretation of SOA 2.0...

In my context SOA 2.0 is of course the merger between SOA and the Web 2.0. It is interesting to see this definition, though. It highlights the importance of realtime which ultimately allows to react to any type of event much faster than by using a data warehouse and any sort of BI.

But is this a reason to promote it to version 2.0?

Progress Software has a leading tool for Complex Event Processing (Apama) that gains more and more visbility within the installed base of SOA customers.

So let's see how the term SOA 2.0 will be defined in the future. Maybe I should call my blog SOA 3.0 or SOA 2.5?  We'll see :)

Technorati Tags: ,,,

Thursday, August 28, 2008

...coming soon

give me some time to get started in my new job at Progress Software - will probably cross-post some stuff from the CRM 2.0 blog...

Progress Software