Cloud Application Architecture Patterns

Chapter 9. Application Migration and Modernization

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 9th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

While an application can be designed new for the cloud, a cloud application often begins as one that runs in traditional IT and then is moved to the cloud.

So far in this book we have assumed that when designing and architecting an application for the cloud, you are creating a new greenfield application from scratch. While greenfield development can be ideal, the reality is that many cloud applications start their lifecycle as traditional IT applications that are later moved to the cloud. These existing applications were designed for traditional IT and not for the cloud. As explained in Chapter 1, legacy applications often embed characteristics that work fine on traditional IT but are poorly suited for cloud computing.

This chapter explores how to move an existing application to the cloud and make it run better on the cloud. For these legacy applications to work well in the cloud, developers need to not only move the application to the cloud ...