scholarly journals Securing Enterprise Applications: Service-Oriented Security (SOS)

2008 ◽  
Author(s):  
Csilla Farkas ◽  
Michael N. Huhns
Keyword(s):  
Enterprise Applications ◽  
Service Oriented

scholarly journals Introduction to Containerization

2020 ◽  
Vol 6 (12) ◽  
pp. 294-300
Author(s):  
Raghav Goel and Dr. Bhoomi Gupta
Keyword(s):  
Large Scale ◽  
Software Engineer ◽  
Service Oriented Architecture ◽  
Use Case ◽  
Production Environment ◽  
Code Base ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Multiple Services ◽  
Local Machine

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

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.

Enterprise Integration With the Structural Services Architectural Style

2019 ◽  
pp. 352-392 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Architectural Style ◽  
Enterprise Integration ◽  
Representational State Transfer ◽  
Advantages And Disadvantages ◽  
Architectural Styles ◽  
State Transfer ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Structural Compliance

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.

Web 2.0

2010 ◽  
pp. 119-134
Author(s):  
Wail M. Omar
Keyword(s):  
Grid Computing ◽  
Web 2.0 ◽  
Health Information ◽  
Service Oriented Architecture ◽  
Bottom Layer ◽  
End Users ◽  
Web 2.0 Technology ◽  
Enterprise Applications ◽  
Service Oriented

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.

Data Loading and Caching Strategies in Service-Oriented Enterprise Applications

2009 ◽  
Author(s):  
Matthieu-P. Schapranow ◽  
Jens Krueger ◽  
Vadym Borovskiy ◽  
Alexander Zeier ◽  
Hasso Plattner
Keyword(s):  
Enterprise Applications ◽  
Service Oriented ◽  
Data Loading ◽  
Caching Strategies

scholarly journals A Transaction-Oriented Architecture for Structuring Unstructured Information in Enterprise Applications

2011 ◽  
pp. 285-299 ◽  
Author(s):  
Simon Polovina ◽  
Simon Andrews
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Added Value ◽  
Formal Concept ◽  
Lack Of Information ◽  
Wide Range ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Information Errors ◽  
Unstructured Information

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.

Designing Enterprise Applications Using Model-Driven Service-Oriented Architectures

2011 ◽  
pp. 132-155 ◽  
Author(s):  
Marten van Sinderen ◽  
João Paulo Andrade Almeida ◽  
Luís Ferreira Pires ◽  
Dick Quartel
Keyword(s):  
Business Processes ◽  
Continuous Change ◽  
Service Oriented Architectures ◽  
Model Driven ◽  
Software Complexity ◽  
Service Oriented Computing ◽  
Management Group ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Common Goals

This chapter aims at characterizing the concepts that underlie a model-driven service-oriented approach to the design of enterprise applications. Enterprise applications are subject to continuous change and adaptation since they are meant to support the dynamic arrangement of the business processes of an enterprise. Service-oriented computing (SOC) promises to deliver the methods and technologies to facilitate the development and maintenance of enterprise applications. The model-driven architecture (MDA), fostered by the Object Management Group (OMG), is increasingly gaining support as an approach to manage system and software complexity in distributed-application design. Service-oriented computing and the MDA have some common goals; namely, they both strive to facilitate the development and maintenance of distributed enterprise applications, although they achieve these goals in different ways. This chapter discusses a combination of these approaches and discusses the benefits of this combination.

Healthcare Collaborative Framework Based on Web 2.0, Grid Computing and SOA

2012 ◽  
pp. 429-452
Author(s):  
Wail M. Omar
Keyword(s):  
Grid Computing ◽  
Web 2.0 ◽  
Service Oriented Architecture ◽  
Data Availability ◽  
Healthcare Applications ◽  
Storage Devices ◽  
Robust Model ◽  
Enterprise Applications ◽  
Open Standard ◽  
Service Oriented

Web 2.0 has been adopted by many as the best way for forming a collaborative framework e.g., sharing resources, experiences, information, knowledge and feedback. A collaborative framework for application to e-health is necessary to provide patients with the awareness that assists in improving their health. Moreover, collaborative framework can be used by physician to exchange experiences and discuss challenge cases. However, the use of Web 2.0 with healthcare applications is not simple as the use of Web 20 with other enterprise applications according to the privacy of healthcare applications, which requires high quality and security of data, availability of resources, maintainability of services, system security, and Quality of Services (QoS). To offer the required requirements, grid computing is proposed here. Grid computing supporting enterprise applications through offering massive resources through resources collaborative framework that is offering power computing, storage devices, and services. The use of grid computing by Web 2.0 requires robust model that is able to deploy, discover, invoke, and integrate resources in open standard format. Therefore, Service Oriented Architecture (SOA) is adopted as a model for managing the mixing between Web 2.0 and grid computing technologies. SOA for Web 2.0 and Grid Computing (SOAW2G) are used throughout this work to offer a fabric for e-health applications.

scholarly journals EDSOA: An Event-Driven Service-Oriented Architecture Model For Enterprise Applications

2011 ◽  
Vol 14 (3) ◽  
Author(s):  
Karina Hauser ◽  
Helgi S. Sigurdsson ◽  
Katherine M. Chudoba
Keyword(s):  
Software Development ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Architecture Model ◽  
Software Complexity ◽  
Enterprise Applications ◽  
Event Driven ◽  
Service Oriented

Enterprise Applications are difficult to implement and maintain because they require a monolith of code to incorporate required business processes. Service-oriented architecture is one solution, but challenges of dependency and software complexity remain. We propose Event-Driven Service-Oriented Architecture, which combines the benefits of component-based software development, event-driven architecture, and SOA.

Sign in / Sign up

Export Citation Format

Share Document