tag:blogger.com,1999:blog-20305189.post114839079222697860..comments2023-09-23T08:32:34.668-07:00Comments on Greg Pavlik: Is SOA an Architectural Style?Greg Pavlikhttp://www.blogger.com/profile/02076590604248408230noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-20305189.post-46713774281196526192012-02-09T14:25:56.851-08:002012-02-09T14:25:56.851-08:00I want to inderstande the difference between SOA a...I want to inderstande the difference between SOA and REST? and can we use REST as an architectural style for SOA,Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20305189.post-9344636401095272832007-11-09T16:13:00.000-08:002007-11-09T16:13:00.000-08:00On the Internet, the Domain Name System (DNS) asso...On the Internet, the Domain Name System (DNS) associates various sorts of information with so-called domain names; most importantly, it serves as the "phone book" for the Internet by translating human-readable computer hostnames, <A HREF="http://www.enterbet.com" REL="nofollow">sportsbook</A>, into the IP addresses, e.g. 66.230.200.100, that networking equipment needs to deliver information. It also stores other information such as the list of mail exchange servers that accept email for a given domain. In providing a worldwide keyword-based redirection service, the Domain Name System is an essential component of contemporary Internet use.<BR/><A HREF="http://www.enterbet.com" REL="nofollow">http://www.enterbet.com</A>Unknownhttps://www.blogger.com/profile/09559440378479313077noreply@blogger.comtag:blogger.com,1999:blog-20305189.post-1148505452446613572006-05-24T14:17:00.000-07:002006-05-24T14:17:00.000-07:00I'm a little suspect that setting up a coffee hous...I'm a little suspect that setting up a coffee house may in practice be different than organizing a data center's software assets. The concern I have is that we both clear about what we are saying and that we are directly solving problems related to business information systems.Greg Pavlikhttps://www.blogger.com/profile/02076590604248408230noreply@blogger.comtag:blogger.com,1999:blog-20305189.post-1148503974153177802006-05-24T13:52:00.000-07:002006-05-24T13:52:00.000-07:00The OASIS SOA RM TC came the same basic conclusion...The OASIS SOA RM TC came the same basic conclusion and defined SOA as an abstract model for architecture. Although the group focused on software architecture practices, it is equally applicable to other domains such as setting up coffee shops etc. The model is at:<BR/>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rmAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-20305189.post-1148417953709388732006-05-23T13:59:00.000-07:002006-05-23T13:59:00.000-07:00Yeah, I love the new acronym. Now all I have to do...Yeah, I love the new acronym. Now all I have to do is make sure I use an 8 point font on my slide-ware ;-)Mark Littlehttps://www.blogger.com/profile/15072917010265365428noreply@blogger.comtag:blogger.com,1999:blog-20305189.post-1148411679034367752006-05-23T12:14:00.000-07:002006-05-23T12:14:00.000-07:00One basic and persistent problem is, I think, that...One basic and persistent problem is, I think, that the term SOA is used to mean different things when its presented to systems implementors vs. IT adopters. Some of the high level presentations you see from companies working in this space do a good job of building a layered stack that provides differentation in this regard, but the stacks tend to lump together under a blob called SOA. At this point, we still wind up with this persistent conceptual disconnect.<BR/><BR/>Anyway, I take it you like my new acronym better?Greg Pavlikhttps://www.blogger.com/profile/02076590604248408230noreply@blogger.comtag:blogger.com,1999:blog-20305189.post-1148407697714351012006-05-23T11:08:00.000-07:002006-05-23T11:08:00.000-07:00First of all I agree that Web Services is no more ...First of all I agree that Web Services is no more SOA applicable than CORBA or DCE when you drill down. However, I think that the current approaches to Web Services evolution (one way messages, concentrating on the message format etc.) make it easier to use Web Services as a SOA implementation. But yes, Web Services can be used without reference to SOA and it's pretty easy to produce a CORBA-with-angle-brackets approach, as we both know: just look at OASIS WS-RF. So I don't think there's any disagreement: Web Services can support SOA, but just because you're using Web Services doesn't mean your "doing SOA". Hey, you should have come to my JavaOne panel session - I said exactly the same thing and I was surprised by the number of people who afterwards thought I was wrong!<BR/><BR/>Secondly, I think SOA is an architectural approach if you take it to mean: loose coupling and message-oriented. Take a look at the work of the OASIS SOA-RM group, for example. BTW, on that basis: we have been doing it for years ;-) We just didn't need a TLA to describe it.<BR/><BR/>Thirdly (;-)) I prefer HTTP too, but unfortunately POX payloads don't scale unless you can get everyone to agree on the message exchange format: which is pretty much where Web Services succeed. I'm sure we've talked about this before, but I still think the two main advantages of Web Services are (fairly) universal adoption and XML/HTTP (the latter influenced the former). If you go the POX route, then you're back to trying to force everyone to agree with your way of interacting with services, which is hard.<BR/><BR/>And finally, I agree with your last sentiments, right up to the SOA 2.0 bit ;-) Yes, the way we're using SOA to build "things" is way more than just services and messages and loose coupling, but I'd argue that we do need a different term for it. In the same way that RPC meant synchronous invocations and yet J2EE, CORBA, DCE or DCOM went way beyond RPC (and yet leveraged it), adding process-oriented workflow, data-oriented interactions, distributed management, distributed transactions etc. but weren't termed RPC 2.0.<BR/><BR/>I still think SOA is an architectural approach, in the same way OO is an architectural approach. I just don't think it goes far up the stack. To describe everything else, you may need another term, but I'd prefer it wasn't SOA, or SOA 2.0.<BR/><BR/>As a slight aside, but it may be relevant to where I'm coming from with this, I often wonder if SOA is a confusing term to some because they've been doing that loose-coupling "thing" way before Web Services hit the hype-curve. It's close to MOMs (though MOMs imply a level of persistence and reliability that SOA doesn't). You only have to look at some major messaging deployments (J2EE, CORBA or DCE based) and it's easy to see what I mean.Mark Littlehttps://www.blogger.com/profile/15072917010265365428noreply@blogger.com