Skip to main content

Build Ultra-Scalable Backends with Pekko and Kubernetes

Image
By
Struggling with delivery, architecture alignment, or platform stability?

I help teams fix systemic engineering issues: processes, architecture, and clarity.
→ See how I work with teams.


This article revisits why Akka became a popular choice for high-performance, message-driven backends—and why its 2024 license change pushed many teams toward open alternatives like Apache Pekko or Rust-based Ractor. It explains how the actor model’s concurrency, fault isolation and distributed design pair naturally with Kubernetes, whose autoscaling, self-healing and container orchestration provide the operational backbone for resilient microservice systems. Running actors as lightweight, horizontally scalable units inside k8s lets teams absorb traffic spikes, recover from failure automatically and deploy across regions or hybrid setups with ease. With a simple deployment YAML, Kubernetes manages replicas, load balancing and availability while the actor system handles concurrency and state isolation. The takeaway: for teams building elastic, robust backends—whether with Pekko, Ractor or legacy Akka—combining actor-based runtimes with Kubernetes creates an architecture that gracefully handles scale, failures and real-world complexity.

Update May 21, 2024: 

Lightbend, the company behind Akka, changed the license from Apache 2.0 to BSL, which makes Akka not really attractive anymore. The new license is in place from Akka 2.7 onwards. 

Pekko is a 2.6x fork of Akka, with the same functionalities,  maintained and further developed by the Apache Software Foundation, and is under Apache Software Licence 2 available.

Ractor is written in Rust, has network communication, single messaging, named actors and a cluster mode, and is under MIT license available.

------------------------------

Building a backend that can handle massive traffic and keep your users happy is tough. We're not talking about a simple website with a few hundred visitors a day. We're talking about high-performance systems that can handle spikes in traffic, process huge amounts of data, and keep chugging along even when things go wrong. I have made some great experiences with Akka as micro service in kubernetes, we use k8s to scale our IoT platform across different regions and hybrid setups. 

Running Akka in k8s is a great match from my point of view, they complement each other perfectly, allowing you to build backend systems that are not only scalable and resilient but also incredibly efficient and easy to manage.

Why Akka?

If you're not familiar with Akka, it's a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM. In plain English, this means it's a framework that helps you build apps that can handle a ton of stuff happening at once, spread the load across multiple machines, and keep running even when things go wrong.

The secret to Akka's power is the Actor Model. Actors are like little independent workers that can communicate with each other by sending messages. This makes it super easy to build complex systems that can scale up or down as needed.

Think of it like this: instead of having one overworked employee trying to juggle a thousand tasks, you have a team of specialists, each handling their own piece of the puzzle. This not only makes things more efficient, but it also makes it easier to recover from failures. If one actor crashes, the rest of the system can keep on running.

Why Kubernetes?

Now, let's talk about Kubernetes, or short k8s. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications, initially developed by Google to handle the infrastructure and applications for GCP.

What are containers? In a nutshell, containers are a way to package up an application and all its dependencies so that it can run reliably across different computing environments. There are multiple container management platforms out there, like Docker Swarm, Openshift, or Kubernetes. I personally like k8s, since it's easier to scale and distribute, plus you can better manage multiple installations in deployment sets, using Namespaces to distinguish between applications, etc etc. Kubernetes handles everything from scheduling containers on different machines to load balancing traffic to ensuring that your applications are always available.

Run Akka with k8s

There are multiple pros running Akka in k8s, first Akka actors are naturally suited to a microservices architecture. Each actor can be thought of as an independent service, handling specific tasks and communicating with other actors through messages. Kubernetes provides the perfect platform for deploying and managing these microservices.

2nd, Kubernetes excels at scaling applications up or down based on demand. With Akka actors running as microservices, you can easily add or remove actor instances to meet changing workloads. This ensures your backend can handle traffic spikes without breaking (given the cluster is set to autoscale). Adding a loadbalancer and scale out to the actors, k8s takes care to start new pods at a given load (scale-out), and also kills pods when the load goes back (scale-down). 

3rd, with Akka's built-in fault-tolerance mechanisms, combined with Kubernetes' self-healing capabilities, I create a backend that can withstand failures. If an actor crashes, Kubernetes can automatically restart it on a different node, ensuring uninterrupted operation. 

Here's a simplified ASCII diagram to illustrate the concept:

Akka with k8s simple architecture diagram


A yaml file for a simple setup looks like this one:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-akka-actor
spec:
  replicas: 3 
  selector:
    matchLabels:
      app: my-akka-actor
  template:
    metadata:
      labels:
        app: my-akka-actor
    spec:
      containers:
      - name: my-akka-actor
        image: my-akka-actor-image:latest
        ports:
        - containerPort: 8080 

---
apiVersion: v1
kind: Service
metadata:
  name: my-akka-actor-service
spec:
  selector:
    app: my-akka-actor
  ports:
    - protocol: TCP
      port: 80  # External port (can be different from containerPort)
      targetPort: 8080 
  type: LoadBalancer

This yaml tells Kubernetes to create three instances of your Akka actor, each running in its own container. Kubernetes will automatically manage these instances, ensuring they are spread across different nodes for high availability. The loadbalancer distributes the load, to have persistent session add a sticky mechanism, ideally with a session token.

If you want to build a backend that can handle anything you throw at it, Akka and Kubernetes can be your new best friends. They offer a scalable, resilient, and efficient solution that can help you deliver amazing user experiences.


Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

How to scale MySQL perfectly

By
When MySQL reaches its limits, scaling cannot rely on hardware alone. This article explains how strategic techniques such as caching, sharding and operational optimisation can drastically reduce load and improve application responsiveness. It outlines how in-memory systems like Redis or Memcached offload repeated reads, how horizontal sharding mechanisms distribute data for massive scale, and how tools such as Vitess, ProxySQL and HAProxy support routing, failover and cluster management. The summary also highlights essential practices including query tuning, indexing, replication and connection management. Together these approaches form a modern DevOps strategy that transforms MySQL from a single bottleneck into a resilient, scalable data layer able to grow with your application. When your MySQL database reaches its performance limits, vertical scaling through hardware upgrades provides a temporary solution. Long-term growth, though, requires a more comprehensive approach. This invo...
Read more

What the Heck is Superposition and Entanglement?

By
This post is about superposition and interference in simple, intuitive terms. It describes how quantum states combine, how probability amplitudes add, and why interference patterns appear in systems such as electrons, photons and waves. The goal is to give a clear, non mathematical understanding of how quantum behavior emerges from the rules of wave functions and measurement. If you’ve ever heard the words superposition or entanglement thrown around in conversations about quantum physics, you may have nodded politely while your brain quietly filed them away in the "too confusing to deal with" folder.  These aren't just theoretical quirks; they're the foundation of mind-bending tech like Google's latest quantum chip, the Willow with its 105 qubits. Superposition challenges our understanding of reality, suggesting that particles don't have definite states until observed. This principle is crucial in quantum technologies, enabling phenomena like quantum comp...
Read more