8 ms·
I think this is really neat. I've never really understood using Serverless platforms for websites and things that process web traffic as there's almost always e
by danpalmer 6y ago
I think this is really neat. I've never really understood using Serverless platforms for websites and things that process web traffic as there's almost always enough that a "real" webserver is quicker, easier, and cheaper.
However, I've seen many things that run a couple of times a day, or in response to a deployment, or things like that, which often need some compute behind them, but for which setting up a little server and hosting it somewhere just to call it once a day feels like so much unnecessary ceremony.
Does this have a maximum function duration? If so this could still rule out this approach.
- munns 6y agoYes, you are still limited to 15 minute maximum duration. - Chris Munns - Lead of Dev Advocacy - Serverless@AWS
- danpalmer 6y agoOk that's not too bad a cap. I can see that working for quite a lot of use cases that aren't serving websites.
- spullara 6y agoGPUs please.
- panabee 6y agooracle plans to ship serverless GPUs in Q12021, according to our oracle rep. hope this means amazon and google are close as well.
- rainforest 6y agoIs there any potential for extending that limit? I work on a product that uses Fargate Spot as a kind-of lambda substitute to run longer-duration tasks consumed from SQS and being able to use lambda to do that would make life easier :)
- JoshTriplett 6y agoLikewise. Doesn't have to be indefinite; 1-2 hours would be wonderful.
- remify 6y agoFor a 1 hour process why not just launch an instance ? You can also probably use a spot instance to be even cheaper.
- JoshTriplett 6y agoInstances take longer to start up; Lambda processes requests in milliseconds or less. Lambda automatically manages a pool for you. If you're running a predictable process and you know how long it'll take in advance, an instance may make sense. If you're running an unpredictable process, where you won't know how long it'll take until it's done, and it might be quite fast, the low startup time and fine-granularity billing helps.
- bpodgursky 6y agoECS (potentially on Fargate) would be a reasonable stack for those tasks, given the 15 minute limit on Lambdas.
- WrtCdEvrydy 6y agoTo be honest, if it's a static site and you just need a little bit of compute... Cloudfront in front of S3 and lambda is probably the cheapest way to give someone a basic website (just a contact form and nothing else)
- Pfhreak 6y agoThis is my go to stack these days for personal projects. (That said, I'm a former AWS dev, so I'm super familiar with these moving parts.) It's easy to develop for, it's easy to automate deployments, I don't have to worry about keeping anything up to date, and I can just focus on the small amount of code I want to write. The most expensive thing is the Route 53 configuration at $0.50/month/domain.
- madoublet 6y agoI love this stack. I recently added AWS SAM to the mix as well so that I can automate deployments. I have always wondered why Route 53 was so expensive relative to the other services. I have a collection of low traffic sites that I run for local businesses and this is always the most expensive part. I guess it's hard to complain about $0.50. But, given I could probably run them all on $5 DO droplet, it ends up costing a little more.
- vagab0nd 6y agoIt's my goto stack as well. However, I haven't been able to get both www->root redirect and http->https redirect working. Do you happen to know if it's possible?
- klohto 6y agowww->root should be handled on DNS, therefore Route53. http->https can be done using CloudFront and Lambda@Edge
- ignoramous 6y agofly.io (upto 8CPUs + 8GiB) and stackpath.com (upto 8CPUs + 32GB) both can run such workloads at the Edge. That said, AWS Fargate and AWS Batch (minus the Edge) are probably comparable services to those than AWS Lambda. [0] https://fly.io/docs/about/pricing/ https://fly.io/docs/about/pricing/ [1] https://www.stackpath.com/products/containers/ https://www.stackpath.com/products/containers/
- austinpena 6y agoAre you familiar with stackpath? Does anyone have words to share about them?
- ignoramous 6y agoStackPath is kind of edge-essential services from Cloudflare and AWS rolled into one. I used StackPath's Serverless functions once before and they worked as advertised (but since moved to Cloudflare Workers).
- austinpena 6y agoThanks for the response. I’m currently using them and liking them. Not as sexy as CF workers but I can have 100 delivery domains per site so my customers can point at me for essentially free.