DISQUS

Daniel · 3 years ago

Hi
In the text you, like most I think, define services to be distributed. I do not understand why everybody introduce that limitation. You can implement a one JVM system in that uses business oriented "services" (interface programing) that locates the service implementors at run or call time. I do not see a fundamental difference in that architecture and the distributed SOA.
Equally I do not think you should consider a architecture as SOA if you have hardcoded the impleremtor of a webservice even if it is business oriented and loosely coupled otherwise...

Perhaps it is sufficent to have a broker between the service requestor and implementor?
That is when you truly have decoupled the system, if the implementor and requestor runns in the same JVM or not does not seem that relevant. (in theory :-) )

//Daniel

Johannes Brodwall · 3 years ago

Hi, Daniel

Thank you for you comment. I recommend that you post it again on TheServerSide reprinting of this blog article at http://www.theserverside.com/discussions/thread...

If you do, I will respond to your reservations.


~Johannes

Chat · 1 year ago

In the text you, like most I think, define services to be distributed. I do not understand why everybody i

Johannes Brodwall · 1 year ago

Thanks for your comment. I've encountered people who talk about non-distributed SOA. I think that is an idea that is totally boring, as it says nothing that hasn't been said for twenty years. The idea escapes my concerns, but at the cost of being vacuous.

Investment Opportunities · 5 months ago

The evolution of SOA Introduce the concepts of services and SOA Design principles of SOA ... The benefits of employing SOA Review of common business goals ... Related articles. Web Application Vulnerability Assessment Essentials ... Cancel. We'd love to hear what you think! Submit ideas or give us feedback ...