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

Explaining the software architecture

For our application, we have combined Domain-Driven Design (DDD) and MVC so our legacy application has layers or tiers.

As we followed these approaches, we have the following categories of classes:

  • Controller: Processes the requests from the browser, invokes the appropriate service, and passes the result to the appropriate view (Thymeleaf template).
  • Bean: Encapsulates the information sent to and received from a web page. This is also known as the ViewModel.
  • Service (domain service): Orchestrates the transaction by obtaining an aggregate from the repository, invoking the appropriate business logic on the aggregate and updating the repository.
  • Repository: The abstraction of the relational database that handles Object Relational Mapping (ORM). Thanks to Spring Data JPA, this is an interface and Spring Boot provides the implementation.
  • Aggregate: An object that is a group of domain objects that can be treated as a single...