README.md in dynoscale_ruby-1.0.1 vs README.md in dynoscale_ruby-1.0.2
- old
+ new
@@ -1,18 +1,22 @@
# Dynoscale Ruby
-#### Simple yet efficient scaling agent for Ruby/Rails apps on Heroku
+#### Simple yet efficient scaling agent for Ruby/Rails apps on Heroku. A better [heroku autoscaling](https://dynoscale.net/blog/why-is-queue-time-more-important-than-backend-request-time-to-auto-scaling) alternative.
## Getting Started
1. Add __dynoscale__ to your app on Heroku: `heroku addons:create dscale`
2. Add the agent Gem to your Gemfile: `gem 'dynoscale_ruby'`
3. Run bundle: `bundle install`
4. Profit! (Literally, this will save you money 😏
The environment variable `DYNOSCALE_URL` must be set in order for your application to communicate with Dynoscale Servers.
+## Status
+
+[](https://badge.fury.io/rb/dynoscale_ruby)
+
## Non-Rails Rack Based Apps
In addition to the above steps, you will need to `require 'dynoscale_ruby/middleware'` and add the `DynoscaleRuby::Middleware` before the `Rack::Runtime` in your application.
## Data Shared with Dynoscale
@@ -22,9 +26,17 @@
* queue measurement data for web and worker dynos
## Worker Adapter
In addition to Web scaling, Dynoscale collects data on Worker jobs too. At this time Sidekiq and Resque are currently supported.
+
+## Why use Dynoscale?
+
+Some blog posts about why Dynoscale is a helpful tool.
+
+* [Why is Queue Time more important than Backend Request Time to auto scaling?](https://dynoscale.net/blog/why-is-queue-time-more-important-than-backend-request-time-to-auto-scaling)
+* [How to setup heroku autoscaling in under 15 minutes?](https://dynoscale.net/blog/how-to-setup-heroku-autoscaling-in-under-15-minutes)
+* [Level up your Heroku autoscaling in 15 minutes](http://localhost:5008/blog/level-up-your-heroku-autoscaling-in-15-minutes)
## Contributing
Bug reports and pull requests are welcome on GitHub at https://github.com/Mjolnir-Software/dynoscale_ruby.