Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
1–10 of 131 posts
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#2We use Lambda monolith usually with a Lambda containing an entire REST JSON API node.js server.
It works very well.
I feel one of the reason why Lambda did not gain fast market traction is because all the initial tutorials focused on having an endpoint for each lambda, which is actually a special optmization edge case that can come later.
Services like Vercel just wrap the Lambda and indeed deploy an entire server to the Lambda and gained a lot of users this way. Lambda Monolith are good replacement to the old Heroky dynos. Lambda monolith are super cheap for B2B SaaS startups with little traffic
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#3The question strikes me as odd. I can't imagine why one would split an API across separate isolated compute nodes. I've used isolated functions in the context of "message orchestration" scenarios, but I'd never do that for an API.
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#4We use Lambda monolith usually with a Lambda containing an entire REST JSON API node.js server. It works very well. I feel one of the reason why Lambda did not gain fast market traction is because all the initial tutorials focused on having an endpoint for each lambda, which is actually a special optmization edge case that can come later. Services like Vercel just wrap the Lambda and indeed deploy an entire server to…
>Lambda did not gain fast market traction is because...
I'll extend this to all three cloud services, and dispute the assertion. Developers are smart and figured out that these serverless platforms are great for APIs even if the initial tutorials didn't present that scenario. Also, the platforms just got better at this over time while those early tutorials were somewhat cast in stone. I've not looked lately, but I would hope that they now have tutorials that show monolith scenarios.
>Lambda monolith are super cheap for B2B SaaS startups
Again, I'll extend this to Azure Functions and Cloud Run. Truly an amazing place we now sit. My first public facing API required me to build a physical machine and place it in a colo facility in town. Now I just run a command-line or check in my code and my API is live.
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#5The issue for me (using GCloud functions) was the cold boot issues, is this more or less fixed now?
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#6Why lambda?
Just run nodejs.
The cloud has made otherwise smart people into unthinking drones.
You don’t need any of the cloud stuff, except a Linux virtual machine. Stop drinking the cloud kool ade, it’s making things much more complex and expensive for questionable gain.
Learn how to, you know, run software on a Linux computer.
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#7Why lambda? Just run nodejs. The cloud has made otherwise smart people into unthinking drones. You don’t need any of the cloud stuff , except a Linux virtual machine. Stop drinking the cloud kool ade, it’s making things much more complex and expensive for questionable gain. Learn how to, you know, run software on a Linux computer.
And suddenly you have to manage an entire Linux server. (-:
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#8Why lambda? Just run nodejs. The cloud has made otherwise smart people into unthinking drones. You don’t need any of the cloud stuff , except a Linux virtual machine. Stop drinking the cloud kool ade, it’s making things much more complex and expensive for questionable gain. Learn how to, you know, run software on a Linux computer.
And suddenly you have to manage an entire Linux server. (-:
Oh the burden.
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#9Why lambda? Just run nodejs. The cloud has made otherwise smart people into unthinking drones. You don’t need any of the cloud stuff , except a Linux virtual machine. Stop drinking the cloud kool ade, it’s making things much more complex and expensive for questionable gain. Learn how to, you know, run software on a Linux computer.
There are plenty of cases where lambda is a better fit than hosting a server. Just like there are plenty of cases where it's not an appropriate fit.
By flat out refusing to consider it, you become as much of a "drone" as the people you call out.
Re: Should you use a Lambda Monolith, a.k.a. Lambdalith, for your API?
#10Why lambda? Just run nodejs. The cloud has made otherwise smart people into unthinking drones. You don’t need any of the cloud stuff , except a Linux virtual machine. Stop drinking the cloud kool ade, it’s making things much more complex and expensive for questionable gain. Learn how to, you know, run software on a Linux computer.
There are plenty of cases where lambda is a better fit than hosting a server. Just like there are plenty of cases where it's not an appropriate fit. By flat out refusing to consider it, you become as much of a "drone" as the people you call out.
>> There are plenty of cases where lambda is a better fit than hosting a server.
Such as?
If it’s regional latency then run a machine in the region.