Live data from Hacker News

Using Amazon Auto Scaling with Stateful Applications

11–12 of 12 posts

Re: Using Amazon Auto Scaling with Stateful Applications

#11

Post by amagnus » Wed, Jun 08, 2016, 8:52 PM UTC

jjeaff wrote: post #7

I would be curious what variance of load would be required for this type of auto scaling to be worth the time vs just putting your own bare metal in a colocation facility or leasing dedicated boxes. The price performance is so much higher on dedicated. Or for that matter, using reserved instances instead of scaling with spot prices.

It comes down to the business decision of going all in with cloud or bare metal. Day to day management of each is pretty different.

Re: Using Amazon Auto Scaling with Stateful Applications

#12

Post by amagnus » Wed, Jun 08, 2016, 8:54 PM UTC

stretchwithme wrote: post #9

You'll want to make sure you don't autoscale just because a shared resource like a database is not working correctly. There's no point in having more instances up if the new ones don't work either. Elastic Beanstalk can be very useful, especially for deploying new versions of your app. It has a CLI that makes it easy to SSH to all of your instances as well. And application environments can be configured to save its l…

Good point, and that's when good monitoring comes into play.

Post reply on HN