You're reading from The Definitive Guide to Modernizing Applications on Google Cloud The what, why, and how of application modernization on Google Cloud

Product type Paperback

Published in Jan 2022

Publisher Packt

ISBN-13 9781800209794

Length 488 pages

Edition 1st Edition

Languages

SQL

Tools

Firebase

Concepts

Cloud Computing

Authors (3):

Jason Marston

Dheeraj Panyam

Steve (Satish) Sangapu

View More author details

Table of Contents (26) Chapters

Preface

1. Section 1: Cloud-Native Application Development and App Modernization in Google Cloud

2. Chapter 1: Cloud-Native Application Fundamentals FREE CHAPTER

3. Chapter 2: End-to-End Extensible Tooling for Cloud-Native Application Development

4. Chapter 3: Cloud-Native Architecture Patterns and System Architecture Tenets

5. Section 2: Selecting the Right Google Cloud Services

6. Chapter 4: Choosing the Right Compute Option

7. Chapter 5: Choosing the Right Database and Storage

8. Chapter 6: Implementing a Messaging and Scheduling System

9. Chapter 7: Implementing Cloud-Native Security

10. Section 3: Rehosting and Replatforming the Application

11. Chapter 8: Introducing the Legacy Application

12. Chapter 9: The Initial Architecture on Google Compute Engine

13. Chapter 10: Addressing Scalability and Availability

14. Chapter 11: Re-Platforming the Data Layer

15. Chapter 12: Designing the Interim Architecture

16. Chapter 13: Refactoring to Microservices

17. Section 4: Refactoring the Application on Cloud-Native/PaaS and Serverless in Google Cloud

18. Chapter 14: Refactoring the Frontend and Exposing REST Services

19. Chapter 15: Handling Eventual Consistency with the Compensation Pattern

20. Chapter 16: Orchestrating Your Application with Google Kubernetes Engine

21. Chapter 17: Going Serverless with Google App Engine

22. Chapter 18: Future Proofing Your App with Google Cloud Run

23. Other Books You May Enjoy

Appendix A: Choosing the Right Migration Strategy

1. Appendix B: Application Modernization Solutions

The infrastructure architecture

Our application is a traditional Java application that runs on Tomcat. It uses MySQL to store the relational data and Redis to store the user sessions. As this is an enterprise application, security, availability, and scalability are all important factors. For this reason, we have placed the data tier into a separate subnet protected by a firewall; likewise, the presentation and application tiers are placed in another subnet, also protected by a firewall. The firewalls are configured so that only the Tomcat servers can connect to the data servers, and only HTTP(S) traffic from the internet is allowed into the Tomcat servers. Finally, a load balancer has been placed in front of the Tomcat servers to support our scalability and availability needs.

The following diagram captures the overall architecture of the infrastructure that houses the legacy application being introduced:

Figure 8.1 – Legacy infrastructure architecture...