I wish DO would open a datacenter in Oceania.
DigitalOcean Functions: A powerful serverless computing solution
51–60 of 93 posts
Re: DigitalOcean Functions: A powerful serverless computing solution
#52[deleted]
Re: DigitalOcean Functions: A powerful serverless computing solution
#53I recently learn about this term, so can someone be kind enough to explain to me ELI5 serverless usage[0], advantages over "traditional" servers and why I should/could care? [0] by usage I mean, I still deploy my monolithic app, or just one function per route?
1. It's trendy
2. It locks you in to a certain vendor
3. It costs more
Re: DigitalOcean Functions: A powerful serverless computing solution
#54Earlier quoted context omitted.
It's probably more that you don't have to shift from DO to AWS because you wanted to run lambda. Although I'm not sure if this product is (yet) compelling enough to keep you on DO.
so this means that DO users have been moving to AWS Lambda?
As serverless has been gaining traction a lot of users have moved from traditional vps deployments to serverless offerings because it is more affordable for sporadic workloads.
Re: DigitalOcean Functions: A powerful serverless computing solution
#55Earlier quoted context omitted.
Cloudflare workers: $0.15 per 1M requests per month, minimum charge of $5 per month. Free tier is 100 000 requests per day Here's the pricing page: https://workers.cloudflare.com/#plans
up to 10ms CPU time per request Not much of a room here it seems. AWS still offers more generous CPU time. In fact any price move by new entrants can be countered by AWS going forward. So AWS users benefit from not moving. Simply wait for others to reduce their prices and expect AWS to do the same.
The key difference is that unlike lambda where you are charged for network waiting time, Cloudflare from what I can tell, doesn't count time the CPU is suspended for networking operations.
I use a cloudflare worker for DDNS updates, and it runs on the free tier. If the 10ms included network time, my worker would consistently timeout, but it hasn't timed out yet so I must conclude that it doesn't count network time.
Re: DigitalOcean Functions: A powerful serverless computing solution
#56AWS x86 Price $0.0000166667 for every GB-second $0.20 per 1M requests Arm Price $0.0000133334 for every GB-second $0.20 per 1M requests DO $0.0000185/GB-second So basically a little higher price for each GB/s but no cost pr request. AWS free tier provides 400,000 GB-s and 1 million free requests per month DO free tier 90,000GB-seconds of usage for free per month So cheaper in some respects compared to AWS. Google and…
Thanks this was the information I was looking for and glad I won't be moving off AWS Lambda anytime soon. Really puzzling why DO would announce a new product and make it more expensive than incumbents. Typically, you would want to undercut existing competitors right out of the gate because your competitors will do it for you....by making the first move to reduce their prices, diminishing your own market. Perhaps ther…
Guess: it's for existing DO users, not for attracting new users. Lock in is very real and for most users mostly fine.
Re: DigitalOcean Functions: A powerful serverless computing solution
#57AWS x86 Price $0.0000166667 for every GB-second $0.20 per 1M requests Arm Price $0.0000133334 for every GB-second $0.20 per 1M requests DO $0.0000185/GB-second So basically a little higher price for each GB/s but no cost pr request. AWS free tier provides 400,000 GB-s and 1 million free requests per month DO free tier 90,000GB-seconds of usage for free per month So cheaper in some respects compared to AWS. Google and…
Thanks this was the information I was looking for and glad I won't be moving off AWS Lambda anytime soon. Really puzzling why DO would announce a new product and make it more expensive than incumbents. Typically, you would want to undercut existing competitors right out of the gate because your competitors will do it for you....by making the first move to reduce their prices, diminishing your own market. Perhaps ther…
Cost isn't everything, especially at low rates. UI, tooling, and even the "it isn't Amazon" tax. AWS can be complicated for small deployments.
Also, they may be charging their best profitable/break-even rate right now, working on the product to get cheaper over time or with scale.
Basically, I challenge the implication that one should not enter a market unless they are cheaper than the competition.
Re: DigitalOcean Functions: A powerful serverless computing solution
#58I recently learn about this term, so can someone be kind enough to explain to me ELI5 serverless usage[0], advantages over "traditional" servers and why I should/could care? [0] by usage I mean, I still deploy my monolithic app, or just one function per route?
With traditional server you keep your webserver running all the time and keep paying for the underlying infrastructure whether irrespective of actual usage.
You can still spawn more instances/containers on demand and autoscale but you need to think about provisioning and how that affects your cost.
With serverless the costing maps directly to usage and scaling is (ostensibly) taken care of for you.
If you have long running workloads that anyways need preallocated infrastructure and forward planning, you likely don't gain much from serverless. If your work can be split into smaller units of executions that can be invoked on-the-fly independently, you will likely benefit from serverless pricing.
Re: DigitalOcean Functions: A powerful serverless computing solution
#59I recently learn about this term, so can someone be kind enough to explain to me ELI5 serverless usage[0], advantages over "traditional" servers and why I should/could care? [0] by usage I mean, I still deploy my monolithic app, or just one function per route?
To a certain extent, serverless actually delivers on the "No sysadmins required" promise that EC2 doesn't really enable (someone still has to manage your EC2 herd's configuration, even if you call that person a "devops engineer").
Re: DigitalOcean Functions: A powerful serverless computing solution
#60I recently learn about this term, so can someone be kind enough to explain to me ELI5 serverless usage[0], advantages over "traditional" servers and why I should/could care? [0] by usage I mean, I still deploy my monolithic app, or just one function per route?
1. It's trendy 2. It locks you in to a certain vendor 3. It costs more
The lock-in part is increasingly untrue. Esp. if you are on gcloud, your functions are not tied to their infra at all. Eg. For nodejs you are just writing express middlewares with no real gcloud infra dependency. You can also use their build packs to run and test the functions locally. gcloud serverless infra is also built on knative so if you have teams with k8s familiarity you can run them on in-house infrastructure.
For AWS lambda I believe it was initially true, but now I believe they also support running arbitrary containers.
The costs more part is very much subject to nature of use case. If you have a lot of small services that are invoked once in a while you can benefit from serverless pricing.