During today’s IT software development the SOA paradigm is nearly dominant. The concept is that there are services (mostly SOAP webservices) and client applications, and these two groups are connected through networks, thus they can solve the problems they are designed for. These services and applications communicate with each other over numerous point-to-point connections, whose maintenance is becoming increasingly difficult. The concept of ESB was created to overcome this problem. Basically it gives us a better and easier way to manage the connections, but today it has some so-called mediation options as well, like filtering messages, routing them by their data or metadata, or transforming data and/or protocol.
In the first two chapters of the thesis I introduce the reader the ESB architecture, and the solution for ESB of two well-known manufacturers (IBM, Oracle). Then I present the Spring Framework through three points:
• how can we make (SOAP) webservices with Spring,
• how can make applications with Spring,
• we can make an ESB system on Spring basis using Spring Integration (SI), which is the main topic of my work
In my thesis I used Spring for the first and third point.
In the fifth chapter I design and implement a SOAP webservice, and I present two ways to run it. The next two chapters is about the design and implementation of an ESB based on Spring Integration, with the imagined integration logic and the required configurations.
The last two chapters describe the testing of the implemented solution and a comparison of the Spring Integration with the previously presented ESB products: I compare the response times of the basic (without SI) webservice with the SI-ESB interconnected system over several test cases, and I present the cons and pros of SI-ESB compared against the two big ESB manufacturers’ product.