scholarly journals Introduction to Containerization

Author(s):  
Raghav Goel and Dr. Bhoomi Gupta

Are you a software engineer/developer/coder or maybe even a tech enthusiast who is thinking of agility, parallel development and reducing cost. In the early twentieth century, we witnessed the rise of Service Oriented Architecture (SOA), which is a software architecture pattern that allows us to construct large-scale enterprise applications that require us to integrate multiple services, each of which is made over different platforms and languages through a common communication mechanism, where we write code and multiple services talk to each other’s for a business use case, but sometimes we end up with one big monolithic code base whose maintenance becomes difficult. Nowadays clients are using cloud and paying for on-demand services without effectively utilizing resources. These problems invite micro-services. In this paper, I am going to discuss how one should use scale application in a production environment and local machine

Author(s):  
Vinay Raj ◽  
Ravichandra Sadam

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.


Author(s):  
José Carlos Martins Delgado

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.


Author(s):  
Surya Nepal ◽  
John Zic

In the Service Oriented Architecture (SOA) model, a service is characterized by its exchange of asynchronous messages, and a service contract is a desirable composition of a variety of messages. Though this model is simple, implementing large-scale, cross-organizational distributed applications may be difficult to achieve in general, as there is no guarantee that service composition will be possible because of incompatibilities of Web service contracts. We categorize compatibility issues in Web service contracts into two broad categories: (a) between contracts of different services (which we define as a composability problem), and (b) a service contract and its implementation (which we define as a conformance problem). This chapter examines and addresses these problems, first by identifying and specifying contract compatibility conditions, and second, through the use of compatibility checking tools that enable application developers to perform checks at design time.


Author(s):  
Andrew Targowski

The enterprise system approach is defined by its evolution and major milestones of architectural planning. The ES architectures are multi-faceted solutions, hence it is defined in the scope of the enterprise organization architecture (EOA), enterprise functional architecture (EFA), enterprise processive architecture (EPA), enterprise information architecture (EIA), enterprise software architecture (ESA), enterprise network architecture (ENA), enterprise service architecture (ESA), business component architecture (BCA), enterprise information infrastructure (EII), and enterprise configurations. A composite ES architecture is presented as a transitional architecture, which is currently practiced by most enterprises. The near future of the ES approach will be rather limited to the ways of delivering ES’ applications within a framework of service-oriented architecture (SOA) and the cloud computing, which satisfies effective large-scale operations. The progressive process of organization/business virtualization and the urgent need for more sustainable enterprise development should lead to new development of enterprise systems.


Author(s):  
Wail M. Omar

Web 2.0 is expected to be the next technology in the interaction between the enterprise applications and end users. Such interaction will be utilized in producing self-governance applications that are able to readjacent and reconfigure the operation framework based on users’ feedback. To achieve this, huge numbers of underneath resources (infrastructures and services) are required. Therefore, this work proposes the merge of Web 2.0 technology and grid computing overlay to support Web 2.0 framework. Such merge between technologies is expected to offer mutual benefits for both communities. Through this work, a model for managing the interaction between the two technologies is developed based on the adapting of service oriented architecture (SOA) model, this model is known as SOAW2G. This model manages the interaction between the users at the top level and resources at the bottom layer. As a case study, managing health information based on users’ (doctors, medicine companies, and others) experiences is explored through this chapter.


SIMULATION ◽  
2018 ◽  
Vol 95 (4) ◽  
pp. 363-381
Author(s):  
Fuyu Sun ◽  
Jianping Zhou ◽  
Shuai Guo ◽  
Yi Li

Service-Oriented Architecture (SOA) has gained considerable popularity for the development of large-scale distributed software systems. The SOA paradigm promotes the reusability and integrability of software in heterogeneous environments by means of open standards. The existing problem is that every service-oriented software development project often requires a customized development process that provides specific service-oriented software in support of requirements unique to that project. To resolve this problem, this study proposes universal service-oriented software (USOS). USOS focuses on the general simulation technology and integrates many features, which are necessary to build a correct and efficient simulation system. It is aimed at providing a professional environment to reduce the cost of modeling as well as the execution time of the simulation for multi-type models. USOS supports many advanced features such as dynamic model template generation, multi-formalism model debugging, flexible model-driven application, etc. Developers may use USOS as an open framework to build, store, and verify models very efficiently. Based on USOS, we have developed a large-scale parallel simulation platform called SIM, which is oriented to test parallel and distributed architectures, and applications in the aerospace domain. This study introduces the distinctive features of USOS for practical implementation of SIM and validates the performance by a prototype system simulation.


Author(s):  
Mohammed Moussa ◽  
Abdelhalim Benachenhou ◽  
Abderrahmane Boumehdi ◽  
Abderrahmane Adda-Benattia

A service oriented architecture for simultaneous access in the field of remote labs has been proposed and validated using stress load testing. The innovation of this work lies on the use of the parameters collected for the typical student and tested with the Artillery.io tool. Then, we have evaluated the performance of the laboratory by defining 5s the maximum waiting time that a request cannot be exceeded. This article also describes a use case showing how this architecture was designed and developed with 109 students.


Author(s):  
Simon Polovina ◽  
Simon Andrews

As 80-85% of all corporate information remains unstructured, outside of the processing scope of enterprise systems, many enterprises rely on Information Systems that cause them to risk transactions that are based on lack of information (errors of omission) or misleading information (errors of commission). To address this concern, the fundamental business concept of monetary transactions is extended to include qualitative business concepts. A Transaction Concept (TC) is accordingly identified that provides a structure for these unstructured but vital aspects of business transactions. Based on REA (Resources, Events, Agents) and modelled using Conceptual Graphs (CGs) and Formal Concept Analysis (FCA), the TC provides businesses with a more balanced view of the transactions they engage in and a means of discovering new transactions that they might have otherwise missed. A simple example is provided that illustrates this integration and reveals a key missing element. This example is supported by reference to a wide range of case studies and application areas that demonstrate the added value of the TC. The TC is then advanced into a Transaction-Oriented Architecture (TOA). The TOA provides the framework by which an enterprise’s business processes are orchestrated according to the TC. TOA thus brings Service-Oriented Architecture (SOA) and the productivity of enterprise applications to the height of the real, transactional world that enterprises actually operate in.


Author(s):  
Muthu Ramachandran ◽  
Pethuru Raj Chelliah ◽  
P. Beaulah Soundarabai

Cloud computing technologies are being used highly successfully in large-scale businesses. Therefore, it is useful for governments to adopt cloud-driven multi-channel, and multiple devices to offer their services such as e-tax, e-vote, e-health, etc. Since these applications require open, flexible, interoperable, collaborative, and integrated architecture, service-oriented architecture approach can be usefully adopted to achieve flexibility and multi-platform and multi-channel integration. However, its adoption needs to be systematic, secure, and privacy-driven. In this context, micro services architecture (MSA), a direct offshoot of SOA, is also a highly attractive mechanism for building and deploying enterprise-scale applications. This chapter proposes a systematic framework for cloud e-government services based on the cloud software engineering approach and suggests a cloud adoption model for e-government, leveraging the benefits of MSA patterns. The proposed model is based on a set of evaluated application characteristics that, in turn, support emerging IT-based technologies.


Sign in / Sign up

Export Citation Format

Share Document