News for hackers. Stuff that matters.
Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by liveoneggs on Wednesday August 08, 2018 @09:27AM (#17715725)
if you're worried about the "zero" traffic situation I am not sure you also need to worry much about the "massive" traffic situation
Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by larrywright on Wednesday August 08, 2018 @09:56AM (#17715983)
Actual use case I heard of: Outage reporting system for a utility. You know, the page you go look at when your power goes out. The majority of the time, this page receives no traffic. When there’s an outage, the traffic spikes immensely. When the outage is over, the traffic drops back to near-zero.
Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by gregmac on Wednesday August 08, 2018 @11:46AM (#17716867)
An interesting way to work around this would be to have the ability to scale with mixed instance types.

For example, your base application runs with t2.micro. As soon as traffic starts going up, you launch additional medium/large instances. The load balancer would have to understand this also, and do weighted routing (ideally based on app server loads) so the first micro instance doesn't handle the same volume of traffic as the rest.

I've never seen a setup like this before, and frankly, part of me wonders whether the savings would be worth the effort of building it in the first place (vs just running with medium instances, or just scaling to dozens of micros to handle the load, or just using serverless).

Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by manigandham on Friday August 10, 2018 @03:30PM (#17736131)
All you need is a CDN. Cheap, easy, and decades of reliability. You don't need infrastructure for this.
Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by wahnfrieden on Wednesday August 08, 2018 @09:40AM (#17715806)
I am sure :)

Our customers are concentrated around N. America, with minimal activity at night and weekends. We have a complex product with a wide surface area. Some of our services don't see usage constantly throughout the day.

Our usage is unpredictable and spiky, worsening our ability to cost optimize EC2 autoscaling.

Then there's staging environments...

Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by liveoneggs on Wednesday August 08, 2018 @11:34AM (#17716766)
The smallest ec2 instance is $4/m on-demand (or $8/m for a usable amount of memory)
Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by wahnfrieden on Wednesday August 08, 2018 @11:42AM (#17716832)
>Our usage is unpredictable and spiky, worsening our ability to cost optimize EC2 autoscaling.

Smallest EC2 instance will fall over with a sudden traffic spike, and requests will fail for the couple minutes it takes for autoscaling to complete.

Additionally for HA, a machine must be able to die without exposing us to the risk of a traffic spike taking us down.

Re:Going Serverless: From Common Lisp and CGI to AWS Lambda ... by Touche on Wednesday August 08, 2018 @10:23AM (#17716200)
Every company has parts of their system that has "zero" traffic from time to time.