Author Boris Lublinski provides an overview of three programming models attempt to go beyond just service invocations by seamlessly incorporating service orchestration support and many of the patterns required for successful SOA implementation. They also serve as a foundation for implementation of the Enterprise Service Bus.
The three models covered in the article are:
- Windows Communication Foundation (Indigo) programming Model from Microsoft, which attempts to simplify service programming by creating a unified OO model for all service artifacts.
- Java Business Integration (JBI) model from Java Community Process, which address complexities and variabilities of services programming through creation of services abstraction layer in a form of a specialized (service) container.
- Service Components Architecture (SCA) from IBM, BEA, IONA, Oracle, SAP, Siebel, Sybase, etc., is based on the premise that a "well-constructed component based architecture with well-defined interfaces and clear-cut component responsibilities can quite justifiable be considered as an SOA" 4.
These programming models attempt to go beyond just service invocations by seamlessly incorporating service orchestration support and many of the patterns required for successful SOA implementation. They also serve as a foundation for implementation of the Enterprise Service Bus. The article will give a brief overview of each of these programming models.
Full article is available here.
/filters:no_upscale()/sponsorship/topic/2c0d72d2-1768-47c2-8f5b-24f3ef0ae0e0/QconNYrsb-1679560094156.png)
/articles/windows-services-reliable-restart/en/smallimage/the-service-and-the-beast-small-1671627853685.jpg)
/articles/how-to-manage-full-stack-java-development-with-hilla/en/smallimage/manage-full-stack-java-development-with-hilla-small-1686055303315.jpg)
/articles/debugging-beneath-trusted-abstraction/en/smallimage/debugging-outside-comfort-zone-diving-beneath-trusted-abstraction-small-1685961994992.jpg)
/articles/delivering-fast-testing-strategies/en/smallimage/deliver-fast-tests-have-to-last-small-1685548178496.jpg)
/articles/eda-mediator/en/smallimage/event-driven-architecture-with-mediator-topology-small-1685547200315.jpg)
/articles/azure-functions-quarkus/en/smallimage/azure-functions-on-quarkus-3-1685542580748.jpg)
/minibooks/architecture-2023/en/smallimage/logo-1685600892155.jpg){kind=logo}
/presentations/lyft-cd-benefits-challenges/en/smallimage/tom-wanielista-small-1685002834068.jpg)
/presentations/green-software-growth/en/smallimage/Marco-Valtas-small-1685609473905.jpg)
/articles/test-automation-ci-cd/en/smallimage/effective-test-automation-approaches-for-modern-CI-CD-pipelines-small-1685355310638.jpg)
/articles/impact-machine-learning-climate/en/smallimage/minimising-the-impact-of-machine-learning-on-our-climate-small-1685091723283.jpg)
/articles/kafka-clusters-cloudflare/en/smallimage/tales-of-Kafka-at-Cloudflare-small-1684768928637.jpg)
Community comments
REST
by Srikanth Shreenivas,
JBI v SCA
by Steve Jones,
Why not version 0.95?
by Johan Eltes,
Re: Why not version 0.95?
by Boris Lublinsky,
REST
by Srikanth Shreenivas,
Your message is awaiting moderation. Thank you for participating in the discussion.
Article is a good read. Some mention of REST style web services would have been good. REST style web services are suitable for scenarios where you are managing resources/entities, and operations are typically expressed in terms of HTTP primitives (GET,PUT, POST, DELETE). There are few frameworks such as Restlet which are focussed towards REST style web services.
In fact, I do believe that WS-Management which is WS standard for resource management, does have some similarity with what REST is trying to accomplish
JBI v SCA
by Steve Jones,
Your message is awaiting moderation. Thank you for participating in the discussion.
Mike Rowley did a cracking overview of SCA and JBI at the Enterprise SOA event in Belgium last week, although he was a bit against JBI for obvious reasons (he works for BEA). As someone who has used the IBM first release SCA and was on JBI I'd say that JBI was never designed for end-users to use, its meant to make integrating products together a much simpler and standards based problem. SCA however is aimed squarely at the developers and making that easy.
JBI has issues to really solve the product integration challenge (needs to be multi-VM at least) but is a good "under the covers" solution to the old problem of it taking longer to integrate the products than actually do the integration to other systems. ( from Mike's blog)
SCA is again early but is a cracking model for design and development of services.
WCF is great for invocation, but IME its weak at the actual design/deploy of the services themselves as the concept of a deployable component/service isn't really baked into .NET in the same way as it is with the Java vendors.
Why not version 0.95?
by Johan Eltes,
Your message is awaiting moderation. Thank you for participating in the discussion.
Thanks for an excellent article. Some feedback related to SCA:
- The article references version 0.9 - why not 0.95, which has been the current version since late August.
- A reference for catch-up on SMOs would be nice. Searching osoa.org for Service Message Object does not give a single hit.
- It would be nice to have the composition model commented.
Although not referenced in the article, I think it is interesting to see the SCA specification (Java binding) line-up to the implementations of dependency injection: Java EE 5, OSGi, SCA...
Re: Why not version 0.95?
by Boris Lublinsky,
Your message is awaiting moderation. Thank you for participating in the discussion.
I am using version 0.9, because this is the one that is implemted in IBM products. As for SMO, the only reference outside IBM presentation, that I know of is in WAS ESB/WPS info center publib.boulder.ibm.com/infocenter/dmndhelp/v6rx...