Internal and External Application Integration through Web Services

You may have heard the theory of the boiling frog. It states that if you place a frog into boiling water, the frog will immediately jump out. In contrast, if you place the frog into cool water and gradually ramp the temperature up to a boil, the frog will never jump out, boiling alive. Another way to look at this theory might be: "If I knew what I know now, would I do it again?" TUSC recently ventured down the path of a soup-to-nuts internal and external application integration project for a client in what we perceived as the most efficient and cost effective manner. Specifically, TUSC implemented a light-weight Service Oriented Architecture (Web Services) wherever it made sense. This white paper will discuss both the good and the bad about the approach that was taken. Although the water reached a temperature of 104 at times, knowing what we know today, TUSC would in fact take this approach again and recommend it to others. It is our belief that Web services will soon replace traditional APIs all together - and for good reason. This self-named light-weight SOA is revolutionary in its potential. Let's begin by discussing the customer, their goals, their architecture, what internal and external application integration was required and the "opportunities" at hand. In the next section, we'll discuss considerations for how you might get started implementing a similar architecture within your organization. Please register to download white paper: