• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
Codemotion Magazine

Codemotion Magazine

We code the future. Together

  • Discover
    • Live
    • Tech Communities
    • Hackathons
    • Coding Challenges
    • For Kids
  • Watch
    • Talks
    • Playlists
    • Edu Paths
  • Magazine
    • AI/ML
    • Backend
    • Frontend
    • Dev Life
    • DevOps
    • Soft Skills
  • Talent
  • Partners
  • For Companies
Home » Backend » Akka and Kubernetes – Technologies give their best when combined
Backend

Akka and Kubernetes – Technologies give their best when combined

Codemotion and Facebook organized the Tech Leadership Training boot camp, heres a personal reportage from one of our attendees.

Last update March 26, 2019 by Fabio Tiriticco

The tech world is an explosive one. So many different products are available out there – and new ones see the light every day. Each tool serves a purpose in a certain area. Be that decision-making, test automation, code analysis, performance metrics, application building, contactless payments, a new IDE or a new programming language – the list could easily fill up the entire article.

Every now and then, something will come up and make a dent in its area. Something that gains adoption and eventually affects or redefines how the industry reasons about something.

This is the case for the two technologies I speak about, Akka and Kubernetes. The main reason for me to craft a talk about them is that, even though they operate at different levels (application the former, infrastructure the latter), their core concepts somewhat overlap.

In particular, they both promise elasticity (ability to scale resources up and down) and resilience (the ability to fully recover a component from failure). This creates confusion and questions such as: does one supersede the other one? Do I need both when I’m already using one of them?

My co-speaker and I spent a great deal of time trying to answer these questions. What made the collaboration especially enriching was that we are both very connected to two different communities (the reactive community and the devops community). We had many long discussions, and distilling a common answer from our different views wasn’t always straightforward!

Fortunately, the outcome of our research has been quite rewarding. We submitted our talk to a variety of different events and the high acceptance rate confirmed that we were indeed shedding light on a real issue.

Our main conclusion is that the combination of both Akka and Kubernetes enables an unprecedented level of control over the elastic and resilient properties of your (micro)services system.

On one hand, Akka

  • Lets you write truly cloud-native stateful services, ready for scalability from day one
  • Helps your application achieve resilience at the level of your own business logic
  • Runs on the JVM, which is the most used runtime environment globally

Kubernetes, on the other hand,

  • Is a great choice for the provision of all cloud resources needed by your services
  • Helps scaling and recovering failing services at an infrastructure level
  • Is offered as a managed service by all major cloud service providers.

Our talk arrives there by first introducing the core concepts about distribution and resilience in a complex system, then going a little more into technical details.

The Codemotion crowd in particular was really interested about the Akka side of the talk, which is probably to be expected as Kubernetes already enjoys greater popularity. There were lots of questions about how Akka and its programming model help achieve resilience and elasticity on the application level, and quite a few folks told us that trying out the combination of the two technologies was on their list.

If you need to operate stateful services in the cloud, Akka and Kubernetes are probably one of the best solutions out there. In case of doubt (or disagreement), feel free to reach out!

facebooktwitterlinkedinreddit
Share on:facebooktwitterlinkedinreddit

Tagged as:Codemotion Berlin Kubernetes

Light up the Spark in catalyst by avoiding UDF
Previous Post
Bridging psychology and game design for a shared advantage
Next Post

Related articles

  • Generating a Kubernetes Manifest with Dekorate the Easy Way
  • What is Reactive Programming and How Can I Benefit from It?
  • Is It Always Best to Reduce Code Lines?
  • All You Need to Know About the Spring Framework
  • Creating a Catalogue with StencilJS
  • Which Skills Do I Need To Work On Innovative IT Projects?
  • How to Boost Performance With Lazy Loading
  • Why You Should Use Typescript for Your Next Project
  • Reactive Programming for Distributed Systems: All You Need to Know
  • Designing and Deploying your MVP with Minimal Resources

Primary Sidebar

Lessons Learned in the Cloud

Dive deep into this whitepaper dedicated to the Cloud and discover more about Kubernetes.

OVH Logo Lessons learned in the cloud

Codemotion Milan 2022

https://youtu.be/ym8iilUy_U0

Latest Articles

developer listening to devops podcast, learn devops

11 DevOps Podcasts You Should Be Listening To

DevOps

Video: How to Use Python for Async Microservices

Microservices

AWS amplify, angular, AWS

Step by Step: Running Angular Applications in AWS

Cloud

django python framework

Top Trending Python Frameworks Today

Languages

Discover More

  • Take Data to the Next Level With Graph Machine Learning
  • Jamstack: Are Static Sites a New Revolution for the Web?
  • Why Companies Are Implementing the Developer Experience Job Position

Footer

  • Magazine
  • Events
  • Community
  • Learning
  • Kids
  • How to use our platform
  • Contact us
  • Write for Us
  • About Codemotion Magazine
  • How to run a meetup
  • Tools for virtual conferences

Follow us

  • Facebook
  • Twitter
  • LinkedIn
  • Instagram
  • YouTube
  • RSS

DOWNLOAD APP

© Copyright Codemotion srl Via Marsala, 29/H, 00185 Roma P.IVA 12392791005 | Privacy policy | Terms and conditions

Follow us

  • Facebook
  • Twitter
  • LinkedIn
  • Instagram
  • RSS

DOWNLOAD APP

CONFERENCE CHECK-IN