Decompose legacy systems on PaaS to build SaaS applications
Manage complex dependencies between service components in a legacy system
From the developerWorks archives
Date archived: November 29, 2016 | First published: January 04, 2013
Increasingly, businesses and government agencies find themselves in the position to replace components of a tightly coupled legacy system with loosely coupled components of a Software as a Service (SaaS) application. Many see Platform as a Service (PaaS) as a better option than using a mainframe for decomposing a legacy system into components and building a SaaS application from them. A major drawback is that dependencies between service components in a legacy system can be very complex — this article provides guidance on decomposing legacy systems in a PaaS environment.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.