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

Chapter 5: Accessing Data in Microservice Architecture

In this chapter, we will focus on accessing the database by using the Ballerina language with respect to monolithic 3-tier architecture-based applications. In the 3-tier architecture model, application logic is contained in the application layer. Single-database access for the entire system and database transaction queries are implemented in the application layer. Building an application that runs in a single database is simpler since we can join tables to query results. A microservice architecture, however, forces developers to have a database for each service. Therefore, we need to come up with a more scalable solution to handle problems related to data consistency in database per service architecture.

Here, we will explore various design patterns and how we can use them to implement the order management system that we discussed in the first chapter. Understanding these concepts and design patterns makes the system much simpler...