Lowering Coupling in Distributed Applications With Compliance and Conformance

2020 ◽  
pp. 35-77
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Web Services ◽  
Distributed System ◽  
Fundamental Problem ◽  
Distributed Applications ◽  
Application Integration ◽  
Architectural Style ◽  
Normal Case ◽  
Data Schema ◽  
Share Data ◽  
Integration Problem

The interaction of applications in distributed system raises an integration problem that application-developing methods need to solve, even if the initial specifications change, which is actually the normal case. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications, since they share data schemas between applications, even if they do not actually exercise all the features of those schemas. The fundamental problem of application integration is therefore how to provide at most the minimum coupling possible while ensuring at least the minimum interoperability requirements. This chapter proposes compliance and conformance as the concepts to achieve this goal by sharing only the subset of the features of the data schema that applications actually use, with the goal of supporting a new architectural style, structural services, which seeks to combine the advantages of both SOA and REST.

Improving the Integration of Distributed Applications

2021 ◽  
pp. 217-232
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Web Services ◽  
Fundamental Problem ◽  
Distributed Applications ◽  
Application Integration ◽  
Data Schema ◽  
Integration Problem

The interaction of distributed applications raises an integration problem that needs to be solved. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications. This is caused by sharing data schemas between applications, even if not all features of those schemas are actually exercised. The fundamental problem of application integration is therefore how to provide at most the minimum coupling possible while ensuring at least the minimum interoperability requirements. This article proposes compliance and conformance as the concepts to achieve this goal, by sharing only the subset of the features of the data schema that are actually used.

Structural Data Binding for Agile Changeability in Distributed Application Integration

2020 ◽  
pp. 51-81
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Web Services ◽  
Structural Data ◽  
Distributed Applications ◽  
Application Integration ◽  
Application Development ◽  
Distributed Application ◽  
Data Schema ◽  
Data Binding ◽  
Integration Problem ◽  
Application Specific

The interaction of distributed applications raises an integration problem that consists in how to satisfy the minimum interoperability requirements while reducing coupling as much as possible. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications. This is caused by sharing data schemas between applications, even if not all features of those schemas are actually exercised. This has its toll in application development agility. This chapter proposes compliance and conformance as the concepts to minimize coupling without impairing interoperability by sharing only the subset of the features of the data schema that are actually used. In addition, data binding between messages and the receiver's schema is done structurally in a universal and application-independent way. This eliminates the need for application-specific stubs and allows clients to use any server with which they comply and servers to replace any server to which they conform.

Improving Application Decoupling in Virtual Enterprise Integration

2020 ◽  
pp. 84-114
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Information Systems ◽  
Fundamental Problem ◽  
Virtual Enterprise ◽  
Collaborative Network ◽  
Application Integration ◽  
Enterprise Integration ◽  
Enterprise Information ◽  
Enterprise Information Systems ◽  
Data Schema ◽  
Integration Problem

The interaction of applications belonging to several enterprise information systems (EIS), forming a collaborative network in a virtual enterprise (VE) context, raises an application integration problem that is even more stringent than within a single EIS, since a VE has a temporary nature and therefore integration requirements can change more frequently. Current integration technologies, such as web services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications. This is caused by sharing data schemas between applications, even if not all features of those schemas are actually exercised. The fundamental problem of application integration is therefore how to provide at most the minimum coupling possible while ensuring at least the minimum interoperability requirements. This chapter proposes compliance and conformance as the concepts to achieve this goal, by sharing only the subset of the features of the data schema that are actually used.

Cloud-Based Application Integration in Virtual Enterprises

2019 ◽  
pp. 46-85 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Information Systems ◽  
Fundamental Problem ◽  
Virtual Enterprise ◽  
Collaborative Network ◽  
Virtual Enterprises ◽  
Application Integration ◽  
Enterprise Information ◽  
Enterprise Information Systems ◽  
Integration Problem ◽  
The Individual

A key characteristic of a virtual enterprise (VE) is the heterogeneity of the applications that compose its enterprise information systems (EIS), since it builds on the EIS of the individual enterprises that are part of the collaborative network of that VE. This raises an application integration problem, which is even more serious than within any given EIS because a VE has a temporary nature, and therefore, integration requirements can change frequently. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than needed, since they require sharing data schemas between interacting applications, even if not all values of those schemas are actually used. The fundamental problem of application integration is therefore how to provide at most the minimum coupling possible while ensuring at least the minimum interoperability requirements. This chapter proposes compliance and conformance as the concepts to achieve this goal.

Enterprise Application Integration (EAI)

2009 ◽  
pp. 837-843
Author(s):  
Christoph Bussler
Keyword(s):  
Enterprise Application Integration ◽  
Application Integration ◽  
Technology Infrastructure ◽  
Application System ◽  
Enterprise Application ◽  
Application Systems ◽  
Share Data ◽  
Integration Problem ◽  
Business Data ◽  
Definition Of

As long as businesses only have one enterprise application or back end application system there is no need to share data with any other system in the company. All data that has to be managed is contained within one back end application system and its database. However, as businesses grow, more back end application systems find their way into their information technology infrastructure managing different specialized business data, mainly introduced due to the growth. These back end application systems are not independent of each other; in general they contain similar or overlapping business data or are part of business processes. Keeping the data in the various application systems consistent with each other requires their integration so that data can be exchanged or synchronized. The technology that supports the integration of various application systems and their databases is called Enterprise Application Integration (EAI) technology. EAI technology is able to connect to back end application systems in order to retrieve and to insert data. Once connected, EAI technology supports the definition of how extracted data is propagated to back end application systems solving the general integration problem.

Enterprise Application Integration

2005 ◽  
pp. 229-232
Author(s):  
Christoph Bussler
Keyword(s):  
Enterprise Application Integration ◽  
Application Integration ◽  
Technology Infrastructure ◽  
Application System ◽  
Enterprise Application ◽  
Application Systems ◽  
Share Data ◽  
Integration Problem ◽  
Business Data ◽  
Definition Of

As long as businesses only have one enterprise application or back-end application system, there is no need to share data with any other system in the company. All data that has to be managed is contained within one back-end application system. However, as businesses grow, more back-end application systems find their way into their information technology infrastructure, managing different business data. These back-end application systems are not independent of each other; in general they contain similar business data or are part of the same business processes. This requires their integration for exchanging data between them. The technology that allows this is called enterprise application integration (EAI) technology. EAI technology is able to connect to back-end application systems in order to retrieve and to insert data. Once connected, EAI technology supports the definition of how extracted data is propagated to back-end application systems, solving the integration problem.

Enterprise Application Integration (EAI)

2011 ◽  
pp. 128-133
Author(s):  
Christoph Bussler
Keyword(s):  
Enterprise Application Integration ◽  
Application Integration ◽  
Technology Infrastructure ◽  
Application System ◽  
Enterprise Application ◽  
Application Systems ◽  
Share Data ◽  
Integration Problem ◽  
Business Data ◽  
Definition Of

As long as businesses only have one enterprise application or back end application system there is no need to share data with any other system in the company. All data that has to be managed is contained within one back end application system and its database. However, as businesses grow, more back end application systems find their way into their information technology infrastructure managing different specialized business data, mainly introduced due to the growth. These back end application systems are not independent of each other; in general they contain similar or overlapping business data or are part of business processes. Keeping the data in the various application systems consistent with each other requires their integration so that data can be exchanged or synchronized. The technology that supports the integration of various application systems and their databases is called Enterprise Application Integration (EAI) technology. EAI technology is able to connect to back end application systems in order to retrieve and to insert data. Once connected, EAI technology supports the definition of how extracted data is propagated to back end application systems solving the general integration problem.

Web Services Architecture Model to Support Distributed Systems

2019 ◽  
Vol 54 (6) ◽  
Author(s):  
Sawsan Ali Hamid ◽  
Rana Alauldeen Abdalrahman ◽  
Inam Abdullah Lafta ◽  
Israa Al Barazanchi
Keyword(s):  
Web Services ◽  
Web Service ◽  
Distributed System ◽  
Modern Technology ◽  
Service Description ◽  
Architecture Model ◽  
Software Applications ◽  
Evolving Model ◽  
The Web

Recently, web services have presented a new and evolving model for constructing the distributed system. The meteoric growth of the Web over the last few years proves the efficacy of using simple protocols over the Internet as the basis for a large number of web services and applications. Web service is a modern technology of web, which can be defined as software applications with a programmatic interface based on Internet protocol. Web services became common in the applications of the web by the help of Universal, Description, Discovery and Integration; Web Service Description Language and Simple Object Access Protocol. The architecture of web services refers to a collection of conceptual components in which common sets of standard can be defined among interoperating components. Nevertheless, the existing Web service's architecture is not impervious to some challenges, such as security problems, and the quality of services. Against this backdrop, the present study will provide an overview of these issues. Therefore, it aims to propose web services architecture model to support distributed system in terms of application and issues.

scholarly journals Http Relay Binding (webHttpRelayBinding) and Crud Contract

2019 ◽  
pp. 51-54
Author(s):  
Dr. Manish L Jivtode
Keyword(s):  
World Wide Web ◽  
Web Services ◽  
Web Service ◽  
World Wide ◽  
Distributed Applications ◽  
Configuration File ◽  
Representational State Transfer ◽  
State Transfer ◽  
Representational State ◽  
Http Protocol

The Broker Architecture became popular involving client and server. Representational State Transfer(REST) architecture is the architecture of World Wide Web. REST uses HTTP protocol based on Servlet and ASMX technology is replaced by WCF web service technology. SOAP and REST are two kinds of WCF web services. REST is lightweight compared to SOAP and hence emerged as the popular technology for building distributed applications in the cloud. In this paper, conducted by exposing a HTTP endpoint address, HTTP relay binding (webHttpRelayBinding) and CRUD contract through interface. The interface is decorated using WebGet and WebInvoke attributes. WCF configuration file created using XML tags for use with REST web service.

Sign in / Sign up

Export Citation Format

Share Document