Monday, June 13, 2016
A separate app doesn't sound like a sensible solution. I'd do the following:
1. Use a job queue, roll out the feature to a subset of users, identify performance bottlenecks and optimise them.
2. Roll out to a larger subset of users and repeat 1.
3. When you're confident that this works good roll out the feature 100%.
At any point in time you can offload database-intensive operations to a read-only replica. I wrote an article (http://www.gregnavis.com/articles/how-to-move-expensive-queries-to-a-cheaper-follower/) how to do this on Heroku PostgreSQL but the technique applies to other RDBMs as well.
--
Greg Navis
I help tech companies to scale Heroku-hosted Rails apps.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAA6WWt-AJ2tavA1b0593r-1RBcYD%3DC55%2BF_juqbe8Mb03k%3D_-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment