If you’ve ever launched a startup, you know how hard it is to find funding. It’s a huge grind just to get from conception to execution without even worrying about profitability yet. But to attract an investor, you have to show consistent revenue growth to prove they will eventually see a return. Many, many startups fail before they reach a Series A. And the industry with the highest startup failure rate? The information industry, at 63%.
Kubernetes has a lot of features and deployment options for running containers. One of these is the StatefulSet. In this blog post, we’ll discuss what a StatefulSet is, what it can be used for, and how to create and update them.
Log messages help us to understand data flow through applications, as well as spot when and where errors are occurring. There are a lot of resources for how to store and view logs for applications running on traditional services, but Kubernetes breaks the existing model by running many applications per server and abstracting away most of the maintenance for your applications. In this blog post, we focus on log management for applications running in Kubernetes by reviewing the following topics.
As a fast-moving startup, you don’t have the luxury of spending days figuring out exactly what you need in a Kubernetes cluster. We’ve been there. To help out, we wrote a whole ebook on the blueprint we followed as we built and deployed our own web app in Kubernetes.
You’ve put in the time applying for tech jobs and have made it to the daunting interview. You know they are going to ask you about Kubernetes, so make sure you are prepared. If you are completely new to Kubernetes we recommend you first read our Kubernetes pronunciation post, so you don’t really embarrass yourself, and then check out the Kubernetes glossary we created to help give you a decent Kubernetes foundation.
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.
