A Model-Driven Architecture Approach to the Efficient Identigication of Services on Service-orientated Enterprise Architecture

The enterprise architecture for abstract services requires efficient development of loosely coupled and interoperable service sets. The existing design method does not always fully exploit the value and importance of engineering investing in existing legacy systems. In this paper, I will show you how to effectively define important services of these legacy systems. This approach focuses on defining these services based on model driven architecture (MDA) approaches. This is supported by guidelines for various possible service types.

Each micro service cooperates with a specific business function and defines only the operations required for that business function. This may seem exactly the same as service-oriented architecture (SOA), but in reality there are some common features in micro service architecture and SOA. Both architectures organize the code into services, both of which define an explicit boundary that represents the point at which the service needs to be separated from another service. However, SOA arises from the need to integrate monolithic applications that publish APIs (usually SOAP based) together. In SOA, integration is highly dependent on middleware, especially Enterprise Service Bus (ESB). The micro service architecture typically uses a message bus, but there is no logic in the message layer - it is used purely to send messages from one service to another. With micro service, development is quick, service changes according to business needs.

This article describes the differences between enterprise application integration and service-oriented architecture. And will clarify many misunderstandings between them. This article is affected by three major sections. The first part outlines enterprise application integration. In the second half, we will outline the service-oriented architecture and Web service. The last section describes the relationship between enterprise application integration and service-oriented architecture.

In this article, I explained the difference between enterprise application integration and service-oriented architecture. In the first part of this article, we will discuss the barriers such as EAI as a tool for enterprise application integration, its advantages in general, disadvantages of the organization, rare skills and conflicting systems. In the second half, we reviewed the service-oriented architecture and explained the principles and requirements for avoiding future problems. Next, I will explain the concept of Web service, then explain the benefits of SOA. Finally, I will explain the relationship between EAI and SOA and explain how these two parties work together.

The service-oriented architecture (SOA) can be categorized as follows; the architecture style as a combination of unique functions of the executive architecture supports service-oriented. SOA services are reusable components used in business processes. This is a logical representation of repeatable business activities with specified results and in some cases consists of other services. (Mark Colan, 2004; Barbara Reed, 2008)