SOA Architecture in ANSP.pdf - Google Drive

skyguide Introducing a SOA Infrastructure

Giovanni Trovatelli | | March 16, 2016 [email protected]

SOABASE: Introducing a SOA infrastructure Giovanni Trovatelli, Senior Project Manager

The existing system landscape at most ANSP’s is the result of a trackcentered architecture grown over years. In a world that is more and more interconnected, services will be created and delivered by specialized organizations. With the new Service Oriented Architecture (SOA), the Swiss ANSP will be able to offer and to consume such services in a flexible and efficient way. The internal project provides the infrastructure needed to do exactly this. Description Service Oriented Architecture (SOA) is being promoted in the industry as the evolutionary step in software architecture to help IT organizations meet their ever more complex set of challenges. Is it real, though, and even if it can be outlined and described, can it really be implemented? Yes it can! But how does SOA work at all? Let’s use the analogy of Lego bricks!

The four characteristics of Lego bricks that are most appropriate for illustrating the strengths of business Services in the context of SOA are the following: -

-

-

-

Lego bricks and bricks are interoperable. Standards-based interfaces are the secret to the bricks’ interoperability. Or to be more precise, it’s the Service contract that matters. We call that encapsulation. Lego bricks are unbreakable. It’s not that Lego brick are truly unbreakable, but rather, that the Lego Group designed them with significant robustness in mind. In SOA we call such a design for robustness “loose coupling”. Lego bricks and bricks are composable. Services can be composed into applications that implement business processes in a flexible way, we call it interoperability. Lego bricks are reusable. Just as you can reassemble Lego in different constructions, you can reuse a specific service in different applications.

Lego Blocks and Service Granularity But what is the best size for a Lego block? The moral here is that fine-grained services by themselves aren’t particularly valuable to the business. But services can also be so coarse-grained that they hinder the flexibility of the business. The optimal granularity for services generally falls somewhere in the middle. Lego and the limits of this analogy Let’s face it: The analogy of Lego and SOA is just an illustrative one: You have to design and build bricks (services) on your one, your “Flight Plan” and my “Flight Plan” are not the same and: You will not change your processes every day so this nice “drag&drop” orchestration of services will add only a limited value. But: The core value (encapsulation, loose coupling, interoperability, reusability) are still true!

LEGO is a trademark of the LEGO Group of companies which does not sponsor, authorize or endorse this content Giovanni Trovatelli Switzerland [email protected] ®

The Project

Mediation

The project supports the Virtual Center initiative of the Swiss ANSP, by providing a modern technical platform to offer and to consume technical services. We are in charge of evaluating, designing and implementing a suitable SOA-based “Common Integration Platform”, also called CIP.

The mediation layer is the platform for SOA applications. The language in this layer is purely canonical, and every service can use any other service. This is the place to implement business logic.

Integration The different phases of the project are: Elaboration of the requirements and creation of the architecture blueprint Evaluation of the responses including the execution of a proof of concept for the short-listed vendors Decision and preparation of contract Rollout of the CIP platform

· ·

· ·

The CIP will be operated in a isolated LAN/WAN on the new virtual environment, dedicated to the CIP and his services. Where are we A small step for a Project Manager, but a big step for an ANSP: That is my intermediate summary of where we are. Topics like Safety, ICT Security and Vertical Integration are in an ongoing definition mode. The cooperation with internal and external suppliers needs to be determined to fulfill existing and future safety requirements. Therefor we will go into a pilot phase after the first implementation, in order to check the designed procedure during NonOperational Mode. The CIP

This layer translates data formats from backend applications to the canonical language in the mediation layer. The integration layer is responsible to do the fine grained communication with backend systems. Infrastructure Caching and Messaging is an infrastructure service used by all of the other layers. Further requirements are: decoupling systems, highavailability on several layers, highly predictable performance in terms of throughput, rich quality of service (persistent and non-persistent delivery, local and distributed transaction support, authentication and authorization, end-to-end message encryption, secure connections, etc.), and zero-downtime for the overall operation. Governance The Governance layer holds tools used to audit, monitor, and administer the CIP, and to enable dynamic policy-based SOA governance by allowing users to manage and enforce cross-functional requirements such as security and compliance independent of their implementation and deployment. Gateway The gateway is the layer where services provided by the CIP are presented to the consumers. The gateway will eventually talk to security and policy enforcement points, it will in rare cases do some simple call routing, it can perform throttling of services, and it will cache results. Conclusion

(ZRH (Datacenter Zurich) will be a copy of GVA (Datacenter Geneva)

SOA is on the roadmap of several ANSP’s. I hope you were able to gain an insight into the topic. Do not hesitate to contact me if you have any further question: [email protected]

LEGO is a trademark of the LEGO Group of companies which does not sponsor, authorize or endorse this content Giovanni Trovatelli Switzerland [email protected] ®