Always-On Enterprise Information Systems With Service-Oriented Architecture and Load Balancing

Always-On Enterprise Information Systems With Service-Oriented Architecture and Load Balancing

Serdal Bayram (Siemens, Turkey)
Copyright: © 2018 |Pages: 23
DOI: 10.4018/978-1-5225-3704-5.ch010

Abstract

In today's digital age, it is essential for a business to provide a seamless and continuous service to its customers and other stakeholders like providers. Such an always-on service is required, not only for the strong competitive environment but also because of the fact that most the stakeholders also have to offer seamless and continuous service to their own stakeholders. In this chain, failure of one of the systems and components even for a short time can result in a disaster in the entire service chain. A wise approach to provide a continuous service should consider all possible failure areas in a computer-based information system. Since hardware and software are vulnerable to a myriad of problems that can halt the normal operation of a system, an ideal solution should not only consider both of these two components, but also should seek to find ways for them to work in support of each other against a malfunction. This chapter is an attempt to develop a model that provides this functionality. Service Oriented Architecture (SOA) is implemented in the model due to its tenets that are suitable for such functionality.
Chapter Preview
Top

Software Component: Service Oriented Architecture

Service-oriented architecture (SOA) and its paradigms provide efficient IT environment for business processes to run and manage them effectively and efficiently. SOA is a framework to address the requirement of loosely coupled, standards-based and protocol-independent distributed computing, mapping enterprise information systems to the overall business process flow (Gong and Janssen, 2012). A SOA-enabled business process uses IT services also called as eservices which are distributed, virtualized and can be consumed 24*7 by overcoming geographic limitations. SOA provides dynamical business processes that can also run across different organizations and are able to be constructed to achieve a higher flexibility and agility. As stated by Aalst et al. 2007, for the last 20 years enterprise information systems have been becoming more “process-aware” instead of “data-aware”. This forces EIS to be designed with business process perspective. Business processes and their mature EIS implementation bring successful results. Business processes of the enterprises are lacking of efficient and successful integration of IT applications to the other key processes. This problem results in time and money consuming issues because data integrity, repeatable and inconsistent tasks and challenging maintenance problems are faced.

Although SOA can be defined in several ways, all definitions can be categorized in two main perspectives, namely business perspective and technical perspective. Business perspective can be analyzed in terms of business processes and business services, whereas technical perspective can be analyzed in terms of software components and operational resources. The two perspectives, their components, and their interrelationships are illustrated in the Figure 1.

Figure 1.

SOA with Technical and Business Perspective (OMG, nodate)

Complete Chapter List

Search this Book:
Reset