3 ms·
I moved away from Rails because the data model didn't fit my app. But I still use it for all the management applications. Here's a writeup I did for EngineYard
by bensummers 16y ago
I moved away from Rails because the data model didn't fit my app. But I still use it for all the management applications.
Here's a writeup I did for EngineYard about the move from Rails to JRuby and my own app 'framework': http://bens.me.uk/2010/jruby-in-practice http://bens.me.uk/2010/jruby-in-practice
- generalk 16y agoFascinating. I'd love to hear about the data model mismatch -- having done mostly CRUD webapps, I'm not really in a position to see that.
- bensummers 16y agoWell, the main problem is that the user data we store is multi-valued. So each attribute can have multiple values in the same 'record'. As you can imagine, Rails doesn't help much in this situation, as it assumes that each column in the databas table has just one value. http://www.oneis.co.uk/technology/object-store http://www.oneis.co.uk/technology/object-store Oh, and each application on a multi-tenant app server can have a completely different schema. Again, there's not much that Rails can do to help. Rails was good to get going, and it helped for the relational stuff in the app. But unsurprisingly, if you try and use it for something it's not designed to do, it's not going to work terribly well. This principle applies to everything.