Live data from Hacker News

Autoscaling on AWS

qzaidi.github.io

1–10 of 29 posts

Re: Autoscaling on AWS

#4
post #2

What CSS/Framework/whatever are you using for that metro-style dashboard?

Thats dashing from shopify. Its really awesome, took me only an hour or so to setup with the integrations. Here's the original https://github.com/Shopify/dashing.

I am using the nodejs port though - npm install dashing-js

Re: Autoscaling on AWS

#5
Great points. Something like logstash for logging (which supports graphite/statsd type output) is a nice addition to the logging setup.

Also, for some apps deploying code during instance launch can be time consuming. Depending on your monitors and auto scale config, this might be acceptable. For some it may be appropriate to put code right in the ami and only ever deploy via new ami.

Re: Autoscaling on AWS

#7
post #6

It's unhelpful to needlessly abbreviate ordinary words, like "infra" for "infrastructure" in the first paragraph.

You are right - committed a fix, but looks like github is taking longer to rebuild the pages.

Re: Autoscaling on AWS

#9
This is good as far as it goes -- nice to see further corroboration that EBS is not always the best solution.

What I'd really like to see is details of how the traffic monitoring works, how you calculate how much extra capacity to spin up, and how quickly you can react to load events.

Re: Autoscaling on AWS

#10
Not to detract from this article explicitly on the subject of AWS, but ... if you are relying on any single cloud provider then you are probably not going to scale beyond a certain point, since it means that reliability (ie. heterogeneity - re: cloud providers, physical/logical points of presence, legal jurisdictions, etc.) is not all that important to you. At a certain point, a cloud provider neutral approach is called for.
Post reply on HN