Since our founding, the SOA Consortium has been exploring the relationship between SOA and other “hot” business and technology topics. Over the last 2.5 years, we have looked into SOA & BPM, SOA & Event Processing, SOA & BPM & Green, and most recently, SOA & Cloud Computing.
To begin our SOA and Cloud Computing exploration, we invited David Linthicum, SOA expert, blogger and founder of Blue Mountain Labs, to speak at our March meeting. The distinctions and connections, according to Dave, are simple. SOA is something you do, an architectural pattern. Cloud computing is an architectural option.
Ever practical, Dave emphasized that cloud computing provides a way to leverage ‘other people’s work’ in your SOA. This shortens the start-up time of SOA, which creates business value quicker. The trick is to determine which services, information, and processes are good candidates to reside in, come from, the clouds. And the place to start, is your architecture. Understand your business drivers, information under management, existing services under management and core business processes.
In addition to understanding your issues, understand the early state of cloud computing, the portability and interoperability issues, and beware of the hidden costs, such as integration.
When we first published the podcast of Dave’s talk, I mentioned Dave had a SOA & Cloud Computing book coming out this summer, well that book, Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide, is now available for pre-order on Amazon.
If you are a SOA practitioner considering Cloud Computing, or a Cloud Computing practitioner considering SOA, check out Dave’s latest book. He’s a welcome voice of reason in a sea of hype.
If you haven’t already, listen to the audio recording of Dave’s talk from our March meeting.
Please please answer my doubt ....
I am not taliking about web services right not now please see later in the section ..
What i understand ... from implementation point of view SOA is not a new concept ... it existed from the very beginning of programming ...
It always depended upon the pogrammer how the person implments the logic ..
as an example .. say
In X organization one has two DB's one in DB2 , the Other in Oracle. Both having customer Entity but in different structure .. Now the challenge is being a senior developer one need not to bring complexity for database acess to junir developer . The development environment is C, pro C,unix and 2 DB system .
What one do
1. Create a common data model
2. create metadata mapping of common logical data model to actual physical model in DB2 , Oracle .
3. store the metadata mapping and db conn parameter in a simple text file
4. create a Proc Wrapper program using to read that file for database access .
5. the junor programmers do not know nothing about DB implementation so from another C program they call the routines in my program and .. Job done ..
This is going on from the very beginning of software programming .. What is new in SOA ????
Web services : yes i understand their utility for B2B or communication between incompatible platforms... but it is the underlying protocol that is important .. it is not a design thing .. it is just an utility just like FTP etc ...before advent of FTP one has to copy data manually in disk and then again put that into other computer ..
similarly web service is a service which is using a secure protocol to transfer data ...
I do not understand why so much HYPE about these two ??
Posted by: sasanka | July 28, 2009 at 02:42 PM