Book Image

Cloud Native Applications with Ballerina

By : Dhanushka Madushan
Book Image

Cloud Native Applications with Ballerina

By: Dhanushka Madushan

Overview of this book

The Ballerina programming language was created by WSO2 for the modern needs of developers where cloud native development techniques have become ubiquitous. Ballerina simplifies how programmers develop and deploy cloud native distributed apps and microservices. Cloud Native Applications with Ballerina will guide you through Ballerina essentials, including variables, types, functions, flow control, security, and more. You'll explore networking as an in-built feature in Ballerina, which makes it a first-class language for distributed computing. With this app development book, you'll learn about different networking protocols as well as different architectural patterns that you can use to implement services on the cloud. As you advance, you'll explore multiple design patterns used in microservice architecture and use serverless in Amazon Web Services (AWS) and Microsoft Azure platforms. You will also get to grips with Docker, Kubernetes, and serverless platforms to simplify maintenance and the deployment process. Later, you'll focus on the Ballerina testing framework along with deployment tools and monitoring tools to build fully automated observable cloud applications. By the end of this book, you will have learned how to apply the Ballerina language for building scalable, resilient, secured, and easy-to-maintain cloud native Ballerina projects and applications.
Table of Contents (15 chapters)
1
Section 1: The Basics
4
Section 2: Building Microservices with Ballerina
8
Section 3: Moving on with Cloud Native

Answers

  1. Both alpha and beta testing are the final stages of the testing process. Alpha tests are done by testers within the developer organization. But beta testing is performed by the end user. Both tests are considered acceptance tests.
  2. The testing method can be separated into two parts as black box testing and white box testing. Black box testing does not require knowledge about the system implementation. Black box testing plays a key role in usability testing. Assume a scenario where users enter an invalid username and password. The user interface should inform the user that this is not the correct combination of username and password. White box testing, on the other hand, requires an internal implementation to perform the test. For example, unit testing checks the internal implementation of a program.
  3. The CI/CD pipeline unifies code changes into a single repository and automates the whole deployment and delivery pipeline. Any change can be deployed to the target platform...