Integrated business‐process driven design for service‐oriented enterprise applications

Author(s):  
Xingdong Shi ◽  
Weili Han ◽  
Yinsheng Li ◽  
Ying Huang
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):  
Athanasios Bouras ◽  
Panagiotis Gouvas ◽  
Andreas Friesen ◽  
Stelios Pantelopoulos ◽  
Spiros Alexakis ◽  
...  

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.


2011 ◽  
pp. 1060-1080
Author(s):  
Minhong Wang ◽  
Kuldeep Kumar

A business process displays complexity as a result of multiple interactions of its internal components and interaction between the process and its environment. To manage complexity and foster flexibility of business process management (BPM), we present the DCAR architecture for developing complex BPM systems, which includes decomposition of complex processes (D); coordination of interactive activities (C); awareness of dynamic environments (A); and resource selection and coordination (R). On the other hand, computing technologies, such as object-oriented programming, component-based development, agent-oriented computing, and service-oriented architecture have been applied in modeling and developing complex systems. However, there is considerable ambiguity involved in differentiating between these overlapping technologies and their use in developing BPM systems. No explicit linkage has been established between the requirement of complex BPM and the supporting technologies. In this study, we use the DCAR architecture as the foundation to identify the BPM requirements for employing technologies in developing BPM systems. Based on an examination of the both sides (BPM requirements and supporting technologies), we present a clear picture of business process complexity with a systemic approach for developing complex BPM systems by using appropriate computing technologies.


Author(s):  
Hailong Sun ◽  
Jin Zeng ◽  
Huipeng Guo ◽  
Xudong Liu ◽  
Jinpeng Huai

Service composition is a widely accepted method to build service-oriented applications. However, due to the uncertainty of infrastructure environments, service performance and user requests, service composition faces a great challenge to guarantee the dependability of the corresponding composite services. In this chapter, we provide an insightful analysis of the dependability issue of composite services. And we present a solution based on two-level redundancy: component service redundancy and structural redundancy. With component service redundancy, we study how to determine the number of backup services and how to guarantee consistent dependability of a composite service. In addition, structural redundancy aims at further improving dependability at business process level through setting up backup execution paths.


Author(s):  
Huy Tran ◽  
Ta’id Holmes ◽  
Uwe Zdun ◽  
Schahram Dustdar

This chapter introduces a view-based, model-driven approach for process-driven, service-oriented architectures. A typical business process consists of numerous tangled concerns, such as the process control flow, service invocations, fault handling, transactions, and so on. Our view-based approach separates these concerns into a number of tailored perspectives at different abstraction levels. On the one hand, the separation of process concerns helps reducing the complexity of process development by breaking a business process into appropriate architectural views. On the other hand, the separation of levels of abstraction offers appropriately adapted views to stakeholders, and therefore, helps quickly re-act to changes at the business level and at the technical level as well. Our approach is realized as a model-driven tool-chain for business process development.


Sign in / Sign up

Export Citation Format

Share Document