What about native NoSQL for a small projects? I mean how fast would it be with MongoDB & GraphQL. How many of those pairs u're able to setup simultaneously?
Well. The only thing do DATA-base stand 4 - the data. I mean types, memory allocation, responsiveness, etc. Any frameworks is stand for frame. So, no any relations. But my point was about GraphQL as ORM replacement. If it possible to say so. Just an analogy.
What about native NoSQL for a small projects? I mean how fast would it be with MongoDB & GraphQL. How many of those pairs u're able to setup simultaneously?
You can do what you want, but the real strength of MongoDB lies in Aggregation framework.
Otherwise, it doesn't even matter which database you choose.
Well. The only thing do DATA-base stand 4 - the data. I mean types, memory allocation, responsiveness, etc. Any frameworks is stand for frame. So, no any relations. But my point was about GraphQL as ORM replacement. If it possible to say so. Just an analogy.
The way I usually use ORM is to attach Properties / Methods to Objects (in Object * Model).
GraphQL goes by a different paradigm.