2 ms·
>Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.) I could be way off here (and I probably am) but shouldn't framew
by brazzledazzle 11y ago
>Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.)
I could be way off here (and I probably am) but shouldn't frameworks abstain from being too opinionated about the particular technologies that you use? The database (or type of db) you choose seems like something that should be based on what your application's requirements dictate not what your framework prefers right?
- adrusi 11y agoMy opinion differs: if you're going to package your tool as a "framework" rather than a "library", you should integrate a large vertical section of the technology being used. This doesn't mean you have to be coupled with a particular database server, but you should at least have special support for one that can be swapped out for something else. If a framework can't offer me this kind of functionality, why would I want to use it over a library with all the control benefits that brings.