Introducing Akka Cloud to Edge Continuum. Build once for the Cloud. Seamlessly deploy to the Edge - Read Blog

The Reactive Principles: Eight Tenets For Building Cloud Native Applications

Jonas Bonér Founder, CTO and Chairman of the Board, Lightbend, Inc.

Eight Principles For Going Reactive 

View on Slideshare

Many people ask us at Lightbend, is there a “right” way to build a cloud native application? We’ve certainly seen a lot of examples of what doesn’t work well–so what have we learned?

Well, we know that building applications for the cloud means embracing a radically different architecture than that of a traditional single-machine monolith, requiring new tools, practices, and design patterns. The cloud’s distributed nature brings its own set of concerns–building Cloud Native, Edge Native, or IoT applications means building and running a distributed system on unreliable hardware and across unreliable networks.

In this presentation by Jonas Bonér, creator of Akka and founder/CTO of Lightbend, we’ll review a set of eight Reactive Principles that enable the design and implementation of Cloud Native applications–applications that are highly concurrent, distributed, performant, scalable, and resilient, while at the same time conserving resources when deploying, operating, and maintaining them.

Watch The Full Presentation (1 hr)

Watch on YouTube

Join Reactive Foundation

As part of the Linux Foundation, the Reactive Foundation is is a vendor-neutral home for Reactive projects and initiatives and is dedicated to being a catalyst for advancing a new landscape of technologies, standards, and vendors. Reactive Foundation is committed to improving the developer experience of designing and building applications and systems based on Reactive Principles, patterns, and projects.

Find out how membership in the Foundation provides a rare, ground floor opportunity to shape the industry direction and adoption of Reactive concepts:



The Total Economic Impact™
Of Lightbend Akka

  • 139% ROI
  • 50% to 75% faster time-to-market
  • 20x increase in developer throughput
  • <6 months Akka pays for itself