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

Testing the Product service

Let's apply the testing principles we learned to the Product service that we have been building so far. We start from a user point of view and hence with acceptance testing.

BDD through Cucumber

The first step is to recall the specification of our product service. In Chapter 4Extending Your Cloud-Native Application, we built a few features on our product service that allowed us to fetch, add, modify, and delete products, and get a list of product IDs given a product category.

Let's represent this as features in Cucumber.

Why Cucumber?

Cucumber allows the expression of behavior in a plain-English-like language called Gherkin. This enables a ubiquitous language from the domain-driven design parlance, so that the communication between the business, development, and testing is seamless and well-understood.

How does Cucumber work?

Let's understand how Cucumber works:

  1. The first step in Cucumber is to express the user story as features with scenarios, and Given-When-Then conditions...