Hacker News Reader

Comment by schneidmaster | Hacker News Reader

Super excited to see Rails 5 hitting stability. I've recently built a production Rails API on 5 (the beta -- it's been shockingly stable) including ActionCable, with a React + React-Router frontend, handling a pretty good-sized production load on Heroku + Passenger. AMA if you want a developer's/user's perspective on Rails 5 :)

View on HN

For reference when you say "pretty good-sized load" what are you referring to?

Thus far, peak at about 3000 REST requests per minute and 400 simultaneous ActionCable (websocket) connections. We're still scaling up the app, as we just launched it about a week ago, but we haven't yet hit the limits of the platform.

one would hope 50 REST requests per second would not be the limit of the platform.

How many dynos does it take to serve that up, just out of curiousity?

Actually just 1 Performance-M dyno. With Sidekiq for external/resource-intensive requests, and a pretty large pool configured in Passenger.

ETA: It doesn't get as much press, but ActiveJob is one of my favorite parts of Rails 5. It's an agnostic implementation of background jobs -- ActiveRecord : (Postgres, Mysql, etc) :: ActiveJob : (Sidekiq, Resque, etc). Very nice, flexible syntax and it helps make your application platform-agnostic.

Second ETA: As rapind pointed out, ActiveJob has actually been available since Rails 4.2.

I think ActiveJob has been in there since 4.1 or 4.2. Agree it's nice to have a standard.

Reply on news.ycombinator.com