Book Image

The Definitive Guide to Modernizing Applications on Google Cloud

By : Steve (Satish) Sangapu, Dheeraj Panyam, Jason Marston
Book Image

The Definitive Guide to Modernizing Applications on Google Cloud

By: Steve (Satish) Sangapu, Dheeraj Panyam, Jason Marston

Overview of this book

Legacy applications, which comprise 75–80% of all enterprise applications, often end up being stuck in data centers. Modernizing these applications to make them cloud-native enables them to scale in a cloud environment without taking months or years to start seeing the benefits. This book will help software developers and solutions architects to modernize their applications on Google Cloud and transform them into cloud-native applications. This book helps you to build on your existing knowledge of enterprise application development and takes you on a journey through the six Rs: rehosting, replatforming, rearchitecting, repurchasing, retiring, and retaining. You'll learn how to modernize a legacy enterprise application on Google Cloud and build on existing assets and skills effectively. Taking an iterative and incremental approach to modernization, the book introduces the main services in Google Cloud in an easy-to-understand way that can be applied immediately to an application. By the end of this Google Cloud book, you'll have learned how to modernize a legacy enterprise application by exploring various interim architectures and tooling to develop a cloud-native microservices-based application.
Table of Contents (26 chapters)
1
Section 1: Cloud-Native Application Development and App Modernization in Google Cloud
5
Section 2: Selecting the Right Google Cloud Services
10
Section 3: Rehosting and Replatforming the Application
17
Section 4: Refactoring the Application on Cloud-Native/PaaS and Serverless in Google Cloud

Summary

In this chapter, we introduced the example legacy application that we will be modernizing as we progress through the book.

We looked at the infrastructure architecture, which is a typical n-tier design, segregating the data and application tiers with firewalls to lock down traffic to only what is specified as necessary for the application to function. We examined the software architecture of the application, noting that we are combining DDD and MVC architectural patterns to have a well-structured and layered application architecture. We also saw how the software architecture makes use of frameworks such as Spring Boot to simplify and standardize our application and minimize plumbing code.

We then reviewed the application code base to understand how dependencies are managed, how to enable Spring Boot Framework components such as JPA Repository management, and how to override the default decisions and functionality provided by the Spring Boot Framework components. We then...