scholarly journals The Strategic Goals of -Using Service Oriented Architecture Principles

2021 ◽  
Vol 6 (2) ◽  
pp. 124-142
Author(s):  
Ashraf Saied Abd El-Naby ◽  
◽  
Yehia M. Helmy ◽  
Emadeldin Helmy Khalil ◽  
◽  
...  
Keyword(s):  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Language Programs ◽  
Software Companies ◽  
Exchange Information ◽  
Service Oriented ◽  
Strategic Goals

Organizations use heterogonous systems and legacy systems, they are implemented at different platforms, different databases, and different language programs. These systems need to exchange information and reuse the same functionality to achieve integration between these systems. Many Software companies failed to achieve information follow and reuse the same functionality. This paper introduces guidelines introduces Service-Oriented Architecture Principles guidelines and rules to help Applications developers to achieve information integrations and reuse the same functionality, SOA principles providing rules and guidelines that specify exactly how solution logic should be decomposed and molded into technology solutions

Patterns for Migration of SOA Based Applications to Microservices Architecture

2021 ◽  
Author(s):  
Vinay Raj ◽  
Ravichandra Sadam
Keyword(s):  
Programming Languages ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Loose Coupling ◽  
Enterprise Service Bus ◽  
Web Based ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Key Features ◽  
Microservice Architecture

Service oriented architecture (SOA) has been widely used in the design of enterprise applications over the last two decades. Though SOA has become popular in the integration of multiple applications using the enterprise service bus, there are few challenges related to delivery, deployment, governance, and interoperability of services. To overcome the design and maintenance challenges in SOA, a new architecture of microservices has emerged with loose coupling, independent deployment, and scalability as its key features. With the advent of microservices, software architects have started to migrate legacy systems to microservice architecture. However, many challenges arise during the migration of SOA to microservices, including the decomposition of SOA to microservice, the testing of microservices designed using different programming languages, and the monitoring the microservices. In this paper, we aim to provide patterns for the most recurring problems highlighted in the literature i.e, the decomposition of SOA services, the size of each microservice, and the detection of anomalies in microservices. The suggested patterns are combined with our experience in the migration of SOA-based applications to the microservices architecture, and we have also used these patterns in the migration of other SOA applications. We evaluated these patterns with the help of a standard web-based application.

Airport Enterprise Service Bus with Self-Healing Architecture (AESB-SH)

2011 ◽  
Vol 1 (1) ◽  
pp. 1-13 ◽  
Author(s):  
Issam Al Hadid
Keyword(s):  
New Technologies ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Self Healing ◽  
Enterprise Service Bus ◽  
Information Accessibility ◽  
Automatic Information ◽  
Healing Agent ◽  
Service Oriented ◽  
Information Interchange

Airports need to adapt new technologies to react effectively and quickly to customers’ needs and to provide a better service such as the electronic ticket. In addition to the challenges of the ability to respond to the growing requirements of the automatic information interchange between the different systems to ensure safe and efficient airport operations. This paper provides an architecture based on the Service Oriented Architecture (SOA) that improves the information accessibility and sharing across the different Airport’s departments, integrates the existing legacy systems with other applications, and improves and maximizes the system’s reliability, adaptability, robustness, and availability using the Self-Healing Agent.

scholarly journals Tape Mbo’e: A First Experimental Assessment

2015 ◽  
Vol 18 (1) ◽  
Author(s):  
Ilse Grau ◽  
Guilherme H. Travassos ◽  
Luca Cernuzzi ◽  
Adolfo Villafiorita
Keyword(s):  
Human Resources ◽  
Service Oriented Architecture ◽  
Evaluation Process ◽  
Legacy Systems ◽  
Construction Process ◽  
Public Agencies ◽  
Experimental Assessment ◽  
Service Oriented ◽  
Economic Constraints ◽  
Initial Results

The development of software not only needs to consider the construction process, but also other aspects such as cost, human resources and communication among stakehold- ers. The lack of simplicity into this context becomes explicit when some restrictions, such as service oriented architecture, must be considered as the basic style to build sus- tainable applications into environments were practitioners are not aware of this software technology. In addition to this, most of the available software processes are not directly applicable nor are they reusable, so learning times becomes risk for the development of the project. Therefore, Tape Mbo’e (TME) has been proposed to support the building of such applications, into development environments like developing countries where we can have economic constraints and scarcity of proficient practitioners. The first application of TME has been to develop a service-based application whose goal is to provide the interoperability among legacy systems of different public agencies in Paraguay. Initial results of this experience indicated the feasibility and simplicity of TME when applied in this field. The evaluation process, its results and conclusions are described in this paper.

Improved Airport Enterprise Service Bus with Self-Healing Architecture (IAESB-SH)

2011 ◽  
pp. 223-240
Author(s):  
Issam Al Hadid
Keyword(s):  
Web Service ◽  
Service Oriented Architecture ◽  
The Self ◽  
Legacy Systems ◽  
Self Healing ◽  
Enterprise Service Bus ◽  
Information Accessibility ◽  
Healing Agent ◽  
Service Oriented

This chapter introduces the different aviation and airport Information Technology systems. Also, this chapter provides architecture based on the Service Oriented Architecture (SOA) that improves the information accessibility and sharing across the different airport departments, integrating the existing legacy systems with other applications, and improving and maximizing the system’s reliability, adaptability, robustness, and availability using the self-healing agent and virtual Web service connector to guarantee the quality of service (QoS).

An Adaptive E-Commerce Architecture for Enterprise Information Exchange

2010 ◽  
pp. 277-293
Author(s):  
Youcef Aklouf ◽  
Habiba Drias
Keyword(s):  
Information Exchange ◽  
Data Exchange ◽  
Service Oriented Architecture ◽  
Enterprise Information ◽  
Product Models ◽  
Exchange Information ◽  
New Models ◽  
Service Oriented ◽  
Process Level

This article contributes to the design of a generic framework for providing a new way to exchange information between enterprises. This concept is a well addressed in the context of B2B standards. Many organizations are increasingly searching for adopting these standards to automate data exchange. But the limit of such models resides in the fact that the content of exchange is defined in several formats which make their use difficult. To overcome this difficulty, we have explored the possibility to integrate new models for describing content involved in B2B transaction which represent a key issue. Our finding establishes the feasibility of integrating product models described by ontology with e-commerce standards especially at the business process level. This article presents a descriptive model allowing partners to exchange information with other organisations without modifying their Information System. The case study also indicates that our system is developed as a Service Oriented Architecture.

Service-Oriented Architecture

2009 ◽  
pp. 130-150
Author(s):  
Matthew Guah
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Software Components ◽  
Application Integration ◽  
Separation Of Concerns ◽  
Enterprise Service Bus ◽  
Exchange Information ◽  
Integration Techniques ◽  
Service Oriented ◽  
Host Organization

For centuries, organizations have been trying to exchange information between their applications by linking them together. However, such application integration has not been as successful as organizations have hoped. With the introduction of SOA, application integration is more successful than the previous integration techniques. SOA is a design philosophy in which resources are cleanly partitioned into remotely accessible software components performing self-contained functionalities, called services. The reinvention of SOA in recent times is attributed to the rise of Web Services, which has become commonly used in VLITP to expose services within the host organization. However SOA can also be implemented with other service exposing techniques. SOA is based on the concept of separation of concerns, realizing that no single entity can be best at everything. SOA is usually implemented using an Enterprise Service Bus (ESB). The ESB is responsible for routing, prioritizing, scheduling, monitoring, and controlling the flow of traffic between services and therefore forms the middleware for Service Orientation.

An Adaptive E-Commerce Architecture for Enterprise Information Exchange

2011 ◽  
pp. 329-345 ◽  
Author(s):  
Youcef Aklouf ◽  
Habiba Drias
Keyword(s):  
Information Exchange ◽  
Data Exchange ◽  
Service Oriented Architecture ◽  
Enterprise Information ◽  
Product Models ◽  
Exchange Information ◽  
New Models ◽  
Service Oriented ◽  
Process Level

This article contributes to the design of a generic framework for providing a new way to exchange information between enterprises. This concept is a well addressed in the context of B2B standards. Many organizations are increasingly searching for adopting these standards to automate data exchange. But the limit of such models resides in the fact that the content of exchange is defined in several formats which make their use difficult. To overcome this difficulty, we have explored the possibility to integrate new models for describing content involved in B2B transaction which represent a key issue. Our finding establishes the feasibility of integrating product models described by ontology with e-commerce standards especially at the business process level. This article presents a descriptive model allowing partners to exchange information with other organisations without modifying their Information System. The case study also indicates that our system is developed as a Service Oriented Architecture.

Business Process Modeling with Services

2013 ◽  
pp. 177-200
Author(s):  
Youcef Baghdadi ◽  
Naoufel Kraiem
Keyword(s):  
Reverse Engineering ◽  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Source Code ◽  
Legacy Systems ◽  
Service Oriented ◽  
Business Functions ◽  
Maintenance Process

Reverse engineering techniques have become very important within the maintenance process providing several benefits. They retrieve abstract representations that not only facilitate the comprehension of legacy systems but also refactor these representations. Business process archaeology has emerged as a set of techniques and tools to recover business processes from source code and to preserve the existing business functions and rules buried in legacy source code. This chapter presents a reverse engineering process and a tool to retrieve services from running databases. These services are further reused in composing business processes with respect to Service-Oriented Architecture, a new architectural style that promotes agility.

Service Identification and Specification with SoaML

2012 ◽  
pp. 102-125 ◽  
Author(s):  
Michael Gebhart
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Cloud Services ◽  
Legacy Systems ◽  
Model Driven ◽  
Service Identification ◽  
Service Oriented ◽  
Service Components ◽  
Business Process Execution ◽  
Architecture Modeling

This chapter focuses on the identification and specification of services based on prior modeled business processes and legacy systems. The resulting service interfaces and service components formalized by using the Service oriented architecture Modeling Language (SoaML) describe the integration of legacy systems into a service-oriented application landscape. The legacy systems provide services for integration purposes and represent the implementations of service components. Additionally, the resulting architecture allows functionality of legacy systems to be replaced with functionality provided by external cloud services. According to model-driven development concepts, the formalized service interfaces and service components as part of the service designs can be used to automatically derive service interface descriptions using the Web Services Description Language (WSDL). These descriptions enable the technical integration of legacy systems. If necessary, service implementations based on the Service Component Architecture (SCA) and the Business Process Execution Language (BPEL) can be generated.

Service-Oriented Architecture and Legacy Systems

IEEE Software ◽  
2014 ◽  
Vol 31 (5) ◽  
pp. 15-19 ◽  
Author(s):  
Nicolas Serrano ◽  
Josune Hernantes ◽  
Gorka Gallardo
Keyword(s):  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Service Oriented
Sign in / Sign up

Export Citation Format

Share Document