4 ms·
Define Ruby on Rails. At that scale don't you have to transition your model layer from ActiveRecord to a service layer that sits on top of your databases? Cer
by pkaler 13y ago
Define Ruby on Rails. At that scale don't you have to transition your model layer from ActiveRecord to a service layer that sits on top of your databases? Certainly at that scale you are going to be using many different types of databases to store different types of data.
- danso 13y agoMaybe it can be defined as the core-front-end is using ActiveRecord (or a NoSQL equivalent) to do most of the DB interaction and the Rails controller and routing mechanisms? By that standard, Twitter wouldn't count (and it isn't on this list), just as Twitter shouldn't be on a Top 10 Drupal sites list since only the dev docs are in Drupal.
- kaonashi 13y agogem 'rails'
- mikkelewis 13y ago@Scribd we built https://github.com/kovyrin/db-charmer https://github.com/kovyrin/db-charmer to manage multiple model connections to separate servers/databases.
- richardjordan 13y agoRails != ActiveRecord This isn't rocket science. You start your project rails new foo. You include gem 'rails' in your Gemfile. You're a rails application. How you architect for growth is beside the point.