Lightbend’s Jonas Bonér on How to Minimize Cloud Native Complexity

Lightbend’s Jonas Bonér on How to Minimize Cloud Native Complexity

Lightbend’s Jonas Bonér on How to Minimize Cloud Native Complexity. Cloud providers will manage complexity and leave developers to focus on business logic. Think of it not as abstraction but as being opinionated.

At its heart, going cloud native is about managing complexity.

“Ten years ago, distributed systems were mainly the domain of academia and a few big companies like Google, Facebook and Amazon,”  Akka framework creator and Lightbend Chief Technology Officer  Jonas Bonér said. “Now the move towards multicore systems, cloud infrastructure, big data platforms and microservices is forcing developers into the distributed world whether they like it or not.”

That means developers have to think about problems they never had to consider when writing monolithic applications that run on a single core on a single node; like what to do when network problems prevent components from talking with each other, or how to handle node failures.

Organizations are only just beginning to really wrestle with the issue. A  recent survey conducted by Lightbend of over 1,000 developers and IT decision-makers found that the majority of respondents believed that either utilizing Kubernetes and containers (34.5%) or moving to a cloud infrastructure provider (23.8%) were the most important aspects of going cloud native. In other words, most are thinking more about cloud infrastructure than they are about writing applications that run well on that infrastructure.

But as Google developer advocate Kelsey Hightower put it: “There’s a ton of effort attempting to ‘modernize’ applications at the infrastructure layer, but without equal investment at the application layer, think frameworks and application servers, we’re only solving half the problem.”

The idea is that cloud providers will manage the deep complexities and leave developers to focus on business logic. You could also think of it not as abstraction but as being opinionated.

The other half of the problem is, in short, managing application-level complexity. “The standard approach to dealing with complexity is to hide it behind a leaky abstraction,” Bonér said. “For example, hide the fact that you’re speaking to a remote service, across the network.”

cloud native serverless contributed sponsored

Bootstrap 5 Complete Course with Examples

Bootstrap 5 Tutorial - Bootstrap 5 Crash Course for Beginners

Nest.JS Tutorial for Beginners

Hello Vue 3: A First Look at Vue 3 and the Composition API

Building a simple Applications with Vue 3

Deno Crash Course: Explore Deno and Create a full REST API with Deno

How to Build a Real-time Chat App with Deno and WebSockets

Convert HTML to Markdown Online

HTML entity encoder decoder Online

How native is React Native? | React Native vs Native App Development

Article covers: How native is react native?, React Native vs (Ionic, Cordova), Similarities and difference between React Native and Native App Development.

Multi-cloud Spending: 8 Tips To Lower Cost

Mismanagement of multi-cloud expense costs an arm and leg to business and its management has become a major pain point. Here we break down some crucial tips to take some of the management challenges off your plate and help you optimize your cloud spend.

The Roadblocks of Cloud Native

Cloud native is a journey, not a destination. A few roadblocks can appear in the way of any journey. The Roadblocks of Cloud Native.

What are the benefits of cloud migration? Reasons you should migrate

To move or not to move? Benefits are multifold when you are migrating to the cloud. Get the correct information to make your decision, with our cloud engineering expertise.

How to Become a Cloud-Native Company and 13 Tools to Get You There

How to Become a Cloud-Native Company and 13 Tools to Get You There. This article explains how to become Cloud Native and recommends specific projects you can start using today.