4 reasons why soa is the problem
DESCRIPTION
Most public sector landscapes today resemble a patchwork of systems stitched together by services and policed by a federation of service busses, integration hubs and identity management systems. The inherent complexity of these landscapes is causing new projects to fail and obstructing the move to mobile devices and a modern user experience. Instead of a narrow focus on replacing legacy systems, the public sector should also invest in new ways to reduce complexity and solve the integration challenge. These slides suggests how the principles of object-oriented design can be applied at a higher level to achieve user-oriented systems integration. A new integration layer is the proposed solution, implementing the principles of abstraction, encapsulation, modularity and hierarchy to manage the complexity of the underlying service architecture.TRANSCRIPT
SOA is theProblem
4 Reasons Why
The Connected Citizen Initiative
Everything should be made as simple aspossible but not simpler.
- ALBERT EINSTEIN -
Too Complex!So many potential points of failure...
Traditional integrated systems are tightly-coupled and highlyinterdependent. A change in one system impacts all theothers.
Lessonsfrom Object-Oriented
Program Design
1. Abstraction
Traditional SOA joins systems together using hundredsor even thousands of unique services with individualinterfaces.
A well-conceived integration layer can replace thesewith less than a dozen standard, abstracted services.
2. Encapsulation
Traditional SOA wears its complexity on its sleeve byexposing hundreds of interdependent parameters.
An integration layer exposes relevant functionality justin time, using the credentials of the user and the state of underlying application data and processes.
3. Modularity
In traditional SOA consistency is not guaranteedbetween services. Every service must be implementedindividually.
An integration layer provides a small set of consistent,predictable services to perform any available underlyingfunction.
4. Hierarchy
Traditional SOA services expose all their parameters atonce leading to unwieldy integration proxies. If the typeof any parameter changes the entire integration canbreak.
An integration layer brokers incremental access tounderlying services, providing only the detail necessary.
For more information on architecting an integrationlayer that solves the SOA problem, visit us.
To be part of the solution, join us!
ccinitiative.wordpress.com