Page History

...

Enterprise Applications - Raymond

Believe or not, the SCA idea orginally comes from the business integration space. I think that's natural because in In a typical enterprise, business functions are implemented using various technologies, business data are represented in different ways and business services are communicated using heterogeneous protocols. To have all the applications in an enterprise talk to each other is a big challenge. On one hand, it's such a pain to learn, develop, deploy and integrate with all kinds of technologies. On the other hand, it's also

The following are common challenges faced by business integrations:

• The design of business applications is tightly-coupled with the IT infrastructure and early decisions have to be made before the real deployment.
• Application developers have to learn many APIs for different protocols/transports beyond the domain knowledge
• Business logic is polluted and coupled by various technology-specific API calls imposed by the IT infrastructure. It's not easy to write and not easy to change.
• It is almost impossible to converge all the applications

...

• onto one technology stack such as web services.

Having a neutral layer SCA tried to componentize and neutralize the business services beyond the traditional hardware, software and network and promotes a unified programming model that works with all kinds of existing technologies will be ideal for business integrations. We should be able to adapt to the heterogenious infrastrcuture instead.How SCA works with existing technologies. One solution that works with everything.

There are different patterns to support the smooth SOA style integration:

• Wrap the legacy application as a service component
• Invoke the lagacy application using an existing protocol
• Expose the new business functions over an existing protocol

...