Book Image

Cloud-Native Applications in Java

By : Andreas Olsson, Ajay Mahajan, Munish Kumar Gupta, Shyam Sundar S
Book Image

Cloud-Native Applications in Java

By: Andreas Olsson, Ajay Mahajan, Munish Kumar Gupta, Shyam Sundar S

Overview of this book

Businesses today are evolving so rapidly that they are resorting to the elasticity of the cloud to provide a platform to build and deploy their highly scalable applications. This means developers now are faced with the challenge of building build applications that are native to the cloud. For this, they need to be aware of the environment, tools, and resources they’re coding against. If you’re a Java developer who wants to build secure, resilient, robust, and scalable applications that are targeted for cloud-based deployment, this is the book for you. It will be your one stop guide to building cloud-native applications in Java Spring that are hosted in On-prem or cloud providers - AWS and Azure The book begins by explaining the driving factors for cloud adoption and shows you how cloud deployment is different from regular application deployment on a standard data centre. You will learn about design patterns specific to applications running in the cloud and find out how you can build a microservice in Java Spring using REST APIs You will then take a deep dive into the lifecycle of building, testing, and deploying applications with maximum automation to reduce the deployment cycle time. Gradually, you will move on to configuring the AWS and Azure platforms and working with their APIs to deploy your application. Finally, you’ll take a look at API design concerns and their best practices. You’ll also learn how to migrate an existing monolithic application into distributed cloud native applications. By the end, you will understand how to build and monitor a scalable, resilient, and robust cloud native application that is always available and fault tolerant.
Table of Contents (20 chapters)
Title Page
Packt Upsell

Data architecture for microservices

One of the key design philosophies of microservices is the bounded context and the service(s) managing the data store. Within a bounded context, multiple services might have access to a common data store, or adopt a per service data store paradigm.

Since there are potentially multiple instances of a service running, how do we make sure the data read/update operations do not lead to a deadlock in resources?

Command Query Responsibility Segregation (CQRS)

CQRS introduces an interesting paradigm challenging the conventional thought of using the same data store to create/update and also query the systems. The idea is to separate the commands that change the state of the system from the queries that are idempotent. The materialized view is an example of this pattern. The separation also gives the flexibility to use a different data model for updates and queries. For example, the relational model could be used for updates, but the events generated from the updates...