http://thinkinginsideabiggerbox.disqus.com/enMon, 29 Jun 2009 02:53:51 -0000http://www.brodwall.com/johannes/blog/2006/07/26/why-i-love-soa-design-business-related-services/#comment-11873122The 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 ...Investment OpportunitiesMon, 29 Jun 2009 02:53:51 -0000http://www.brodwall.com/johannes/blog/2006/07/26/why-i-love-soa-design-business-related-services/#comment-3874289Thanks 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.jhannesTue, 18 Nov 2008 02:50:48 -0000http://www.brodwall.com/johannes/blog/2006/07/26/why-i-love-soa-design-business-related-services/#comment-3870410In the text you, like most I think, define services to be distributed. I do not understand why everybody iChatMon, 17 Nov 2008 20:37:35 -0000http://www.brodwall.com/johannes/blog/2006/07/26/why-i-love-soa-design-business-related-services/#comment-1796627Hi, Daniel<br><br>Thank you for you comment. I recommend that you post it again on TheServerSide reprinting of this blog article at <a href="http://www.theserverside.com/discussions/thread.tss?thread_id=41836" rel="nofollow">http://www.theserverside.com/discussions/thread...</a><br><br>If you do, I will respond to your reservations.<br><br><br>~JohannesJohannes BrodwallThu, 14 Sep 2006 13:24:49 -0000http://www.brodwall.com/johannes/blog/2006/07/26/why-i-love-soa-design-business-related-services/#comment-1796626Hi<br>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. <br>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...<br><br>Perhaps it is sufficent to have a broker between the service requestor and implementor? <br>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 :-) )<br><br>//DanielDanielThu, 14 Sep 2006 05:31:39 -0000