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. Docker has a container life cycle much like threads. A Docker container can be in Running, Paused, Restarting, and Exited states. Running is the state where the Docker container is executing. While it is running, you can pause the container. The Restarting state comes when the Docker image is restarting. When the Docker container is stopped, it goes to the Exited state.
  2. Both Docker Swarm and Kubernetes can be used for container orchestration. Docker Swarm comes with Docker itself, which has built-in features to perform container orchestration. Kubernetes, on the other hand, provides multiple features, including autoscaling, load balancing, and log monitoring. Deciding which platform to use depends on the architectural requirements of the system. Both products are good at container orchestration and are widely used in production systems.
  3. Kubernetes has different types of objects for performing different tasks. The following are some of the objects used in Kubernetes...