Agreed, really would like to see more technical information about this. A deeper dive is preferred...
Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
11–18 of 18 posts
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#12I was really hoping for a bit more meat in this article. Perhaps some discussion on their caching strategy, or how they're building their JSON (i.e. traditional model-based #to_json approach, or something along the lines of Rabl).
Agreed, not much to look at here. I would also be interested in hearing why they decided to roll their own platform instead of using a PaaS, given the small team size.
Because they are engineers working on their own things with no red-tape?
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#13I was really hoping for a bit more meat in this article. Perhaps some discussion on their caching strategy, or how they're building their JSON (i.e. traditional model-based #to_json approach, or something along the lines of Rabl).
Thanks for the RABL reference (https://github.com/nesquena/rabl), interesting stuff, perfect timing for one of my projects.
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#14I was really hoping for a bit more meat in this article. Perhaps some discussion on their caching strategy, or how they're building their JSON (i.e. traditional model-based #to_json approach, or something along the lines of Rabl).
You could start with sharing how many instances you had at the peak, that would be useful.
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#15This article doesn't really bring anything new to the table - folks have been using this setup for a long time. They could at least talk about how they're managing deployment and scaling under high loads (manual? automated?), or how they're splitting the DB requests between the master and the slave under Rails.
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#16I was really hoping for a bit more meat in this article. Perhaps some discussion on their caching strategy, or how they're building their JSON (i.e. traditional model-based #to_json approach, or something along the lines of Rabl).
You could start with sharing how many instances you had at the peak, that would be useful.
Agreed. More details on if and how automatic scaling was implemented would be good too.
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#17This scales well for reads, but not for writes. The single MySQL instance is still handling all writes and (in it's current form) will have to be scaled vertically.
Re: Scaling a Rails Webservice on AWS/EC2 for a #1 iPhone and iPad App
#18I was really hoping for a bit more meat in this article. Perhaps some discussion on their caching strategy, or how they're building their JSON (i.e. traditional model-based #to_json approach, or something along the lines of Rabl).
Thanks for the RABL reference ( https://github.com/nesquena/rabl ), interesting stuff, perfect timing for one of my projects.
I'm using this on a project right now and am finding a lot of successes derived from its use. We tried to build our JSON in the model using the traditional #to_json/#as_json approach in Rails, but found this was falling on its face when our data model became more complex (which, itself, is probably a code smell, but that's another story).
Good luck! I hope it brings you success.