Prologue—the need for an ESB

It's 9AM Monday. After weeks of work, your team has almost completed a difficult systems integration project. Your system was entirely based on a Java Messaging System (JMS) interface, and you had to integrate it with a different team's web services based system. It meant that your team had to write "glue code" to handle data translation between the two systems, but all that was behind you now, so you could get back to concentrating on finishing up the actual business logic code for the integrated system.

And then, your boss appears at your office door and casually announces that there is one more integration needed for the system. But this time, you have to integrate the system with an older legacy system that is text file and FTP based. Text files! Suddenly you see weeks of writing more new glue code to handle data transformation, protocol conversion, and who knows what else.

How long would it be until you would be able to get back to being able to focus on your "real job" of working on the business logic challenges that your system was intended to solve? What you need is a tool that will enable you to connect these systems together.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.191.147.190