If we make a little stat, 25 tables with 750 db fields means 30 fields per table.
It's not a problem with rails.
25 tables is not a problem with rails.
Nothing is really a problem with rails.
The most important (it's true for every language / framework you'll use) is:
* how do you think your traffic will be
* does your application need to be responsive on one single request or does it need to handle a lot of connections?
Rails slowing is due to:
* databases issues (wrong index, queries who ****** index => likes '% ... %', OR operator etc...
* design errors
* implementation errors (like doing a .uniq or a .sort on a 100.000 cells array instead of asking database to do it)
This said, rails is slower than Java or C. If you need a "real-time" application, rails is not the best choice. On the other hand, if you just need a framework / language to write good code fast, rails is perfect for this. Need to know if you're ready to handle application growing by rewriting code to handle it.
PS: je viens de tilter que tu étais francais. Si t'as du mal a comprendre mon anglais pourrave, je peux traduire, ce sera avec plaisir ^^
Last edited by Mulasse (2011-01-11 20:59:45)