4 ms·
I 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
by jherdman 15y ago
I 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).
- stuartkhall 15y agoThanks for the feedback, i'll try and cover all that in a future post.
- bgentry 15y agoAgreed, 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.
- hello_moto 15y agoBecause they are engineers working on their own things with no red-tape?
- jrnkntl 15y agoThanks for the RABL reference (https://github.com/nesquena/rabl https://github.com/nesquena/rabl), interesting stuff, perfect timing for one of my projects.
- jherdman 15y agoI'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.
- alain94040 15y agoYou could start with sharing how many instances you had at the peak, that would be useful.
- sgerrand 15y agoAgreed. More details on if and how automatic scaling was implemented would be good too.