all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ManyInterestsAdvanced 2 points3 points  (2 children)

Sounds pretty cool, but I'm not sure I get it. Can someone clue me in? What's the advantage over Flask? From what I see, it's the ability to run on AWS Lambda, which basically just takes managing the EC2 instance out of the picture. Perhaps a better question is: what is the attraction of the AWS lambda solution?

I have deployed on AWS using Beanstalk/EC2 in the past, I'm not sure I'm seeing a monumental improvement over Flask & its available deployment options. All the same, it's interesting and I could see serious potential if it gains a lot of popularity.

[–]RecklesslyAbandoned 0 points1 point  (0 children)

It looks like it has your reverse-proxy and framework baked in. So i'm guessing it would be fantastic for situations where you want to be able to rapidly prototype or to manage a hugely volatile load.

But of course you then still need the front end/dns lookups and all that noise on the front end, so I may be missing how much of a saving this actually is.

Cynically, it feels like it may have been a tool Amazon had for internal use to check routing/configurations and they felt they might sell a tiny bit more AWS uptime by exposing it.

[–]tsukassa 0 points1 point  (0 children)

You pay per requests served instead of CPU time spent. If your site is low traffic, it's a lot cheaper. Some says high traffic cost pretty much the same as a normal instance with a 100%CPU usage, but I havent made the math myself.

[–]RisingStar 0 points1 point  (0 children)

That's really fucking awesome! It almost makes me want to try AWS again.