You kind of have to put an RDBMS into the mix because RoR, as a soup to nuts implementation, is tightly coupled to it for persistence. If Twitter chooses to keep RoR it will have to moderate the I/O its DBs see (caching, more iron) or move to a cloud based DB (SimpleDB, BigTable, etc.). In either case the solution will be messy. I agree that Twitter is more a messaging protocol than an MVC application. Such apps would benefit more from a tool like say Erlang than a web-based CRUD framework.
You kind of have to put an
You kind of have to put an RDBMS into the mix because RoR, as a soup to nuts implementation, is tightly coupled to it for persistence. If Twitter chooses to keep RoR it will have to moderate the I/O its DBs see (caching, more iron) or move to a cloud based DB (SimpleDB, BigTable, etc.). In either case the solution will be messy. I agree that Twitter is more a messaging protocol than an MVC application. Such apps would benefit more from a tool like say Erlang than a web-based CRUD framework.