Serverless - fully managed, request based, on demand
View All Tags
Last year when I left my job I wanted to see whether I could build something without the help of all the internal tools I'd been using for the last 5 years. I had a great chance to change anything I wanted within my own stack. That's when the Group Expense with Ease site was born. Today I am celebrating a year since its initial release which I have celebrated with what else than a rewrite.
I was super excited to hear the news about Remix 3 stable being released last week. Similarly to SvelteKit 3 I wanted to run it in AWS Lambda. For SvelteKit I've built kit-on-lambda and I was curious if something similar could be done for Remix as well.
In this article I am going to try to explain how much compute cost at AWS. I will compare three options: EC2, Fargate and Lambda.
Node.js 24 runtime is available on AWS Lambda from 25th November 2025. It removes support for callback-based function handlers. In this article I will go through things which you should know before you upgrade your runtime.
First of all, a big shout out to Martin Damovsky for providing re:Watch service where you can rewatch all the sessions from re:Invent 2025.
What is Bun and why you should use it? Also everything is more fun with AWS Lambda, right?
In this short article you will learn what does it mean when your Lambda transitions to inactive state and how to deal with it.
You can use our CDK construct @beesolve/lambda-keep-active which invokes your Lambda functions regularly so they won't transition into inactive state.
When people compare things like on-prem vs cloud or vps vs serverless they tend to compare just the initial cost and the running cost. Very few people I've met are fully aware of things like maintenance cost, hardware deprecation, flexibility, scaling and all the hidden costs which you only find out after a few months/years of running your service online.
Each solution has it's fit, you just need to know the distinction. For me it goes like this:
Recently I've been talking to people on various meetups about the Serverless technology and I noticed pattern - lot of people think about serverless as limitation rather than solution to real problems.
I've decided to bust a few myths I've been hearing repeatedly lately regarding the whole Serverless ecosystem. I am going to focus on AWS serverless technologies not serverless technology in general.
I have spent 2 days postponing very weird bug with @types/aws-lambda in my serverless project. Finally I decided to fight the fight and try to understand what's going on.