6 ms·

I'd agree on IaaS/PaaS being the main driver. Id guess that everyone is running away from serverless offerings from all the main cloud providers. It's just day

I'd agree on IaaS/PaaS being the main driver. Id guess that everyone is running away from serverless offerings from all the main cloud providers. It's just day 1 lock in to a platform with no shared standards. It's very uncompetitive and kind of slow to innovate.

discodave 2y ago
Amazon loves it when you run idle EC2 instances ($$$) rather than using Lambda. Most real workloads I've seen (at 3 startups, and several teams at Amazon) have utilization under 10%.
- _heimdall 2y ago
  That's really where you see that no answer is right across the board. I worked at a very small startup years ago that leaned heavily on EC2. Our usage was pretty bipolar, the service was along the lines of a real-time game so we either had a very heavy work load or nothing. We stood up EC2 instances when games were lice and wound them down after. We did use Lambda for a few things, mainly APIs that were rarely used or for processing jobs in an event queue. Serverless has its place for sure, but in my experience it have been heavily over used the last 3-5 years.
- Dylan16807 2y ago
  I think the solution to that problem is usually to have fewer and smaller EC2 instances. And you only need to get utilization up to like 15% to make reserved instances significantly better than lambda.
jiggawatts 2y ago
We’re migrating over a hundred apps to Azure App Service. One has an issue with the platform-enforced HTTP timeout maximum values. I migrated that app back to a VM in an hour. It turns out that the “integration” for something like App Service (or CloudRun or whatever) is mostly just best practices for any kind of hosting: parameters read from environment variables, immutable binaries with external config, stateless servers, read only web app folders, monitoring with APMs, etc… Sure, you’ll experience lockin if you use Durable Functions or the similar Lambda features… but no worse than any other workflow or business rules platform. Ask people how easy it is to get off BizTalk or MuleSoft…

discodave 2y ago

Amazon loves it when you run idle EC2 instances ($$$) rather than using Lambda. Most real workloads I've seen (at 3 startups, and several teams at Amazon) have utilization under 10%.

_heimdall 2y ago
That's really where you see that no answer is right across the board. I worked at a very small startup years ago that leaned heavily on EC2. Our usage was pretty bipolar, the service was along the lines of a real-time game so we either had a very heavy work load or nothing. We stood up EC2 instances when games were lice and wound them down after. We did use Lambda for a few things, mainly APIs that were rarely used or for processing jobs in an event queue. Serverless has its place for sure, but in my experience it have been heavily over used the last 3-5 years.
Dylan16807 2y ago
I think the solution to that problem is usually to have fewer and smaller EC2 instances. And you only need to get utilization up to like 15% to make reserved instances significantly better than lambda.

jiggawatts 2y ago

We’re migrating over a hundred apps to Azure App Service. One has an issue with the platform-enforced HTTP timeout maximum values. I migrated that app back to a VM in an hour. It turns out that the “integration” for something like App Service (or CloudRun or whatever) is mostly just best practices for any kind of hosting: parameters read from environment variables, immutable binaries with external config, stateless servers, read only web app folders, monitoring with APMs, etc… Sure, you’ll experience lockin if you use Durable Functions or the similar Lambda features… but no worse than any other workflow or business rules platform. Ask people how easy it is to get off BizTalk or MuleSoft…