Tightly coupled web Services in SOA

Introduction: Learn about the pros and cons of tight coupling and loosely coupled Web Services, and the scale changes brought about by tight coupling. This article provides examples of criteria for determining the performance of tightly coupled Web Services during testing.

Introduction

My Developerworks series articles, use SLAs in a WEB services context, discuss how to eliminate the risks posed by vulnerabilities and how to integrate WEB services into a service level agreement AGREEMENT,SLA) Guaranteed Enterprise Application integration (Enterprise application Integration,eai) architecture. My other Developerworks series work with Web Services in Enterprise-wide Soas discusses load balancing Web services and how to identify the radio frequency (Radio Frequency IDENTIFICATION,RFID) Web Services is integrated into EAI applications. This series also discusses how to develop risk management Web services, migrate legacy service components to discover Web services, and how to use IBM WebSphere? MQ Development WEB Services to integrate SAP with IBM? DB2 and Oracle are integrated.

In each of these articles, I'm trying to explain how a service-oriented architecture (service-oriented Architectures,soa) is loosely coupled to Web services and other interactive software agents. In general, I think you might need to be tightly coupled to some Web services if the resources are not sufficient due to the size of the changes and the speed of execution is critical.

Applications, systems, and networks typically develop faster than their given resource capacity, which includes message queues available to Web services. This poses a security and performance problem, and any time that any operation exceeds the maximum capacity can cause the system overload of the messaging Web services.

In this article, we will look at:

• The contrast between tight coupling and loose coupling.

• Why tightly coupled web Services are required.

• How synchronous business functions are handled in the form of asynchronous, loosely coupled Web services.

· How the coupling of WEB services can switch from loose coupling to tight coupling.

• What criteria should be used to determine performance.

• What are the constraints on determination?