Cloud native

See how the Ballerina programming language has constructs that seamlessly map to network programming concepts such as services and network resources. It also comes with built-in language support to deploy Ballerina applications on the cloud using Docker and Kubernetes.

In a microservice architecture, smaller services are developed, deployed, and scaled individually. These disaggregated services communicate with each other over the network forcing developers to deal with the fallacies of distributed computing in their application logic. For decades, programming languages have treated networks simply as I/O sources. The sections below demonstrate a few of Ballerina's inherent capabilities to develop distributed services effectively and the cloud-native deployment process that is provided as part of the programming experience.

Network-friendly type system

Ballerina's type system is specifically focused on aiding the development of networked and distributed applications. Ballerina is a null-safe language with built-in support for popular wire formats JSON and XML, and seamless conversions between JSON and user-defined types.

Get started

The sample below demonstrates a few simple usages of json and xml types.

import ballerina/io;

public function main() returns error? {
    string name = "Katie Melua";

    // XML literal.
    xml album = xml
        <name>Piece By Piece</name>
        <song>Spider's Web</song>
        <song>Nine Million Bicycles</song>
    io:println("XML Value: ", album);

    // Extract the list of song names from the XML value using a query expression.
    string[] songs = from var song in album/<song>
    io:println("Extracted song names: ", songs);

    // JSON literal.
    json jAlbum = {
        "name": (album/<name>).data(),
        "artist": name,
    io:println("JSON value: ", jAlbum);

    json artistName = check jAlbum.artist;
    io:println("Album artist: ", artistName);

The Ballerina source file is compiled and executed in the following manner.

$ bal run xml_json_sample.bal


Compiling source

Running executable

XML Value: <Album>
        <name>Piece By Piece</name>
        <artist>Katie Melua</artist>
        <song>Spider's Web</song>
        <song>Nine Million Bicycles</song>
Extracted song names: ["Spider's Web","Nine Million Bicycles"]
JSON value: {"name":"Piece By Piece","artist":"Katie Melua","songs":["Spider's Web","Nine Million Bicycles"]}
Album artist: Katie Melua


Services in Ballerina work with a listener object and can have one or more resource methods that contain application logic. The listener object provides an interface between the network and the service. It receives network messages from a remote process according to the defined protocol (e.g., HTTP, GraphQL). Next, it translates them into calls on the resource methods of the services that have been attached to the listener object.

Get started

Below is a simple Hello World service to get you started.

import ballerina/http;

service on new http:Listener(9090) {

    resource function get greeting() returns string {
        return "Hello, World!";

The Ballerina source file is compiled and executed in the following manner.

$ bal run hello.bal

You view the output below.

Compiling source

Running executable

$ curl http://localhost:9090/greeting
Hello, World!

Ballerina services come with built-in concurrency. Every request to a resource method may be handled in a separate strand (a concurrency unit in Ballerina), which gives implicit concurrent behavior to a service.

Some protocols supported out-of-the-box are:

Async network protocol

In the request-response paradigm, network calls are blocking calls. However, blocking an OS thread to perform a network interaction is very expensive. That’s why many other languages supported async I/O, and with that, you have to implement complicated logic to handle asynchronous events using techniques such as callbacks and promises. Ballerina’s request-response protocols are implicitly non-blocking and will take care of asynchronous invocations.

Get started

The code snippet below shows a call to a simple HTTP GET request endpoint.

import ballerina/http;
import ballerina/io;

public function main() returns @tainted error? {
    http:Client clientEP = check new ("");
    string payload = check clientEP->get("/v2/5ae082123200006b00510c3d");

Although the above get operation is seemingly a blocking operation, internally, it does an asynchronous execution using the non-blocking I/O, where the current execution thread is released to the Ballerina runtime scheduler to be used by other Ballerina strands. After the I/O operation ends, the program execution automatically resumes from where it was suspended. This pattern gives you a much more convenient programming model than handling the non-blocking I/O manually while providing maximum performance efficiency.

Client objects

Client objects allow Ballerina developers to communicate with a remote process that follows a given protocol. The remote methods of the client object correspond to distinct network messages defined by the protocol for the role played by the client object.

Get started

The sample below sends out a tweet by invoking the tweet remote method in the twitter client object.

import ballerina/io;
import ballerinax/twitter;

configurable string apiKey = ?;
configurable string apiSecret = ?;
configurable string accessToken = ?;
configurable string accessTokenSecret = ?;

// Twitter package defines this type of endpoint
// that incorporates the twitter API.
// We need to initialize it with OAuth data from
// Instead of providing this confidential data in the code
// we read it from a configuration file.
twitter:Client twitterClient = check new ({

public function main() returns error? {
    twitter:Tweet status = check twitterClient->tweet("Hello World!");
    io:println("Tweeted: ",;

Code to Cloud

Not so long ago, as a developer, you only had to think about writing a program (and tests), building it, and running it. Today, you also need to think about various deployment options such as Docker, Kubernetes, serverless environments, and service meshes. However, this deployment process is not a part of the programming experience.

Ballerina provides a unique developer experience to move from code to cloud. The Ballerina compiler can be extended to read the source code and generate artifacts to deploy your code into different clouds. These artifacts can be Dockerfiles, Docker images, Kubernetes YAML files, or serverless functions.

From code to Kubernetes

Kubernetes is the preferred platform for running applications with multiple microservices in production. It can be used for automating deployment and scaling, and the management of containerized applications. Kubernetes defines a set of unique building blocks that need to be defined as YAML files and deployed into the Kubernetes cluster.

However, in many cases, creating these YAML files could be out of your comfort zone, and thereby, the Ballerina compiler can create these YAML files while compiling the source code. The code below shows the build option you need to use to do this.

The following code snippet shows how the Ballerina compiler can generate YAML files to deploy your code to Kubernetes.

import ballerina/http;

service /hello on new http:Listener(9090) {
    resource function get sayHello() returns string {
        return "Hello, World!";

Building the source with bal build --cloud=k8s will generate the Kubernetes YAML files and Docker image that are required to deploy the hello application into Kubernetes.

Building the source with bal build --cloud=docker will generate the Docker image and Dockerfile.

From code to AWS Lambda

AWS Lambda is an event-driven, serverless computing platform. Ballerina functions can be deployed in AWS Lambda by annotating a Ballerina function with the @awslambda:Function annotation, which should have the function (awslambda:Context, json) returns json|error function signature.

The sample below illustrates a simple echo function with AWS Lambda annotations.

import ballerinax/awslambda;

// Annotating a function with the `@awslambda:Function` annotation 
// generates artifact for an AWS Lambda function.
public function echo(awslambda:Context ctx, json input) returns json {
    return input;

From code to Azure Functions

Azure Functions is a serverless solution that allows you to write less code, maintain less infrastructure, and save on costs. Ballerina functions can be deployed in Azure by annotating a Ballerina function with @azure_functions:Function.

import ballerinax/azure_functions;

// HTTP request/response with no authentication.
public function hello(@azure_functions:HTTPTrigger {authLevel: "anonymous"} string payload)
                        returns @azure_functions:HTTPOutput string|error {
    return "Hello, " + payload + "!";

CI/CD with GitHub Actions

In a microservice architecture, continuous integration and continuous delivery (CI/CD) is critical in creating an agile environment to incorporate incremental changes to your system. Different technologies provide this CI/CD functionality, and very recently, GitHub has introduced GitHub Actions, which is now available for general usage. GitHub Actions is a convenient mechanism for implementing CI/CD pipelines using their workflow concept right from your GitHub repositories.

With the Ballerina GitHub Action, it is straightforward to create a Ballerina development environment with built-in CI/CD.