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

API design concerns

The APIs are meant to be consumed and define how the API can be consumed. APIs specify the list of commands/operations as well as the format/schema of those commands that are required for interaction with the API.

When defining a REST API, the key abstraction of information is the resource. A resource is defined as a conceptual mapping to a set of entities. API design is centered around the resource that forms the nucleus of the design. Uniform Resource Identifier (URI), operations (using HTTP methods), and resource representations (JSON schema) are built keeping the resource in mind. It becomes very important to have the right abstraction of the resource to enable consumption, re-usability, and maintainability of the API.

The resource can point to a single entity or a collection of entities. For example, a product is a singular resource, whereas products are a collection of resources. We will cover the design guidelines at two levels:

  • How to identify the right level of...