It’s no secret that AWS Lambda adoption has grown steadily since AWS first released it in 2015—and for good reason. The benefits of adopting Lambda are many: leveraging Lambda eliminates the need to provision and manage servers, enabling teams to just focus on their code without the mental and operational overhead of worrying about the underlying infrastructure.
Serverless computing has taken off in recent years as engineering organizations have shied away from the complexity and cost that comes with managing physical servers and even virtual machines hosted on a cloud like AWS. If you are interested in serverless options on AWS, you should be comparing Lambda and ECS Fargate to figure out what fits your use case best. In this blog post we will compare these two AWS services in the following areas...
Lambda is an AWS service that allows you to run your code completely in the cloud without the need for on-prem servers. As the world has shifted away from on-prem and toward serverless computing, Lambda has grown in popularity: 1700 companies report using Lambda as part of their data infrastructure in StackShare.
Marc Andreessen famously said, “Software is eating the world.” Dr. Steve Willmott subsequently retorted, “APIs are eating software.” This is because API based architectures are enabling companies to get away from monolithic architectures and move to microservices. Innovative, disruptive companies like Netflix, Airbnb, Uber, Square, and Slack all build their infrastructure and technology using APIs.
Helm is a popular open-source tool used to manage and configure your Kubernetes cluster. Basically, it is a package manager (think Homebrew or NPM) built for Kubernetes. It helps automate processes like installing, configuring, upgrading, and removing items. This post will give you a brief introduction to Helm and how it might help you manage your Kubernetes cluster.
We’ve all been there. A new tool is trending, it is getting mentioned all over the place, and you get dropped into a conversation about it. The last thing you want to do is embarrass yourself by pronouncing something wrong and revealing you don’t know anything about the latest thing. We want to make sure you avoid that happening. When it comes to Kubernetes, there are really only four terms that you might need some help with pronouncing.
