In 2021, it’s common practice for businesses to use a pay-as-you-go/use pricing model. It’s no different with Amazon. It’s also the primary reason why this article is such an important read for all those looking to reduce their AWS Lambda costs.
In this article, we will go over some actionable strategies to optimize the cost relating to our AWS Lambda usage.
One of the main reasons for choosing to move into the cloud is the ability to reduce costs. It’s essential to optimize how much you spend, so you only pay for what you need and only when you need…
We’ve seen time and again how serverless architecture can benefit your application; graceful scaling, cost efficiency, and a fast production time are just some of the things you think of when talking about serverless. But what about serverless security? What do I need to do to ensure my application is not prone to attacks?
One of the many companies that do serverless security, Protego, came up with an analogy I really like.
“It’s a bit like riding in an Uber vs. taking your own car. Sure, the drivers are probably more professional and perhaps better trained. And the flexibility of…
Function as a service (FaaS) offerings like AWS Lambda are a blessing for software development. They remove many of the issues that come with the setup and maintenance of backend infrastructure. With much of the upfront work taken out of the process, they also lower the barrier to start a new service and encourage modularization and encapsulation of software systems.
Testing distributed systems and serverless cloud infrastructures specifically is always a source of long discussions. Some people prefer the local approach…
So without further ado, here we go.
Java has been in service for decades and is, to this day, a reliable option when choosing the backbone of your stack. With AWS Lambda is no different as it makes a strong candidate for your functions.
Reliable and well-tested libraries. The libraries will make life easy for you through enhanced testability and…
Running any application in production assumes reliable monitoring to be in place and serverless applications are no exception.
As modern cloud applications get more and more distributed and complex, the challenge of monitoring availability, performance, and cost get increasingly difficult. Unfortunately, there isn’t much offered right out of the box from cloud providers. Although you can’t fully understand what’s happening just with CloudWatch alone, it is a great place to start and have it as the first line of defense for ensuring service availability and performance.
Let’s explore the basics and more complex use cases for monitoring your Lambda functions…
In this article you’ll find out how to 10x your development speed with local serverless debugging.
Questions such as “what happens when you scale your application into millions of requests?”, “what to expect when going serverless?”, “how does it look like?”, or “how is it to build applications on serverless and work locally?” will be addressed.
In the development world, the ultimate goal is to increase the business value that you can add to your product. And that’s the whole goal of this article — show how to increase development speed to reach that goal faster.
As everything good in life, serverless also comes with its downsides. One of them is the infamous “cold start”. In this article, we’ll cover what they are, what influences serverless startup latency, and how to mitigate its impacts in our applications.
Cold start refers to the state our function when serving a particular invocation request. A serverless function is served by one or multiple micro-containers. When a request comes in, our function will check whether there is a container already running to serve the invocation. When an idle container is already available, we call it a “warm” container. …
Serverless lets you deploy applications far away in a data center of a cloud provider. This relieves you of the lion’s share of operational burdens. The more you buy into your cloud provider’s ecosystem, the less you have to do yourself: no more OS updates or database bugfix installations.
But you still need to do some operation-related work on your own. For instance, monitoring your application to know what’s going on in that far away data center.
Usually, the monitoring journey of a new software product in the cloud goes like this:
The first version gets built with just basic…
Another generic error message from our favorite FaaS provider AWS Lambda.
And again, there are multiple reasons why this issue could arise. Let’s first look at the basics of AWS Lambda to get a better intuition for when things go wrong later.
Lambda is an asynchronous event-based service at heart. The Lambda service asynchronously calls your functions — this doesn’t mean that all events are handled asynchronously, but relates mainly to the programming model you have to use inside your function.
This shouldn’t be confused with the event handling of Lambda, which can be synchronous and asynchronous.
When building serverless applications, Lambda functions often form the backbone of the system. They might provide just a few lines of code, but these lines are usually what hold the whole architecture composed of many managed services together.
Event-driven architecture is what this style is called, and it’s most prevalent in serverless applications. API gateways collect requests from your users, convert them to events, and send these along the way. Sometimes an upstream service, like DynamoDB or SQS, can handle such an event directly to save on Lambda invocation costs.
More often than not, we need to apply some validation…