It is commonly believed that DCOM/CORBA were the earliest avatars of SOA. But in today's world, the term SOA has been used to describe nearly every architecture where components/objects/services/ applications interact. That is the source of all the ambiguity.
In my view, the primary difference between distributed computing and SOA is that there is no level of intimacy in the latter paradigm. Nothing is taken for granted and the unreliability of any given service is part of the initial design consideration. This could not be done with distributed computing. Each part was essential to the whole. On Apr 28, 10:06 am, Gunawan Hadikusumo <[email protected]> wrote: > I don't really agree if you said "disconnection". SOA is a service provided > to the clients without the needs of the clients to know > all the basics information such as the database name etc etc...everything is > hidden from the clients excepts the functionalities.. > and the clients only get the sets of API to be used to the get what they > want. Google Map API for instance. The clients do not need to know from > which database the information is called even 90% percent of mapping process > and search is done on Google server and the clients just render it. > Just like DCOM in 90's, 90% workload is done on the service providers. So > for me SOA is just like a brand new name for DCOM. The main concept is still > the same just bit of enhancement in transportation. > -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
