SERVICE ORIENTED ARCHITECTURE: BUSINESS AND TECHNOLOGY PERSFECTIVE

SOA or Service Oriented Architecture is a term that is a trend in the latest technology in the world of IT. Referring to the name Service Oriented Architecture is an approach in designing (architect) systems where services exist in each existing system. In this case, the components provide a certain type of business service (service) such as: making payments, transferring payments, checking the status of bank accounts, and so on.

Figure 1. SOA component (Source: Paul C. Brown, "Implementing SOA: Total Architecture in Practice", 2008, Addison Wesley Professional, ISBN-10: 0-321-50472-0 ISBN-13: 978-0-321- 50472-2.)



In general, it can be said that SOA is a standard, framework-based architecture that allows systems to integrate data previously only stored in a meeting in various locations or sources. In other words, SOA is an architecture that supports business integration as a connected service and becomes a path to innovation. (SOA is also a technology-based business strategy and evolutionary results to integrate various sources of information from different source code or platforms).

The figure below gives a special description of the process and abstraction of SOA

Figure 2.: SOA Abstraction and Process (Source: Norbert Bieberstein, et al., "SOA Executing: A Practical Guide for Service-Oriented Architect", 2008, IBM Press, ISBN-10: 0-13-235374-1 ISBN -13: 978-0-13-235374-8.)

In Figure above, SOA extraction is a very important chart in the process of developing SOA. In general, systems connected to SOA consist of the current system, systems related to Customer Service, ERP and also the Web. In the above approach it can be concluded that the Web Service Components and Web Service APIs will be connected to SOA Absorption.

The SOA text is loose coupled, which means that a service can be called by another program / service without the caller program that needs to pay attention to where the service location is called and what platform / technology is used by the service. Loose coupling is very important for SOA because thus calling a service by other services can be done at run-time.

Figure 3.: Illustration of SOA Service (Source: 2. Paul C. Brown, "Succeeding with SOA: Realizing Business Value through Total Architecture", 2007, Addison Wesley Professional, ISBN-10: 0-321-50891-2 ISBN- 13: 978-0-321-50891)

For example, a Flight core application provides a service ticket booking, so other applications such as flight schedules, payment gateways, Flight Details etc. can call the service flight booking without needing to know where the flight schedule is in the network and the calling technique that must be used. This is in contrast to the tight coupling approach where in this case each flight application above must have a flight schedule function in it so that it will be difficult and require large costs / resources if necessary to change the logic from flight schedule to new business requirements inside each application.

It can be concluded that SOA is a solution to a variety of platforms and requests for interopability of the system.

No comments:

Post a Comment

Pages