It seems that NoSQL is better for denormalized, but RDBMS is better for normalized. Still, many RDBMS can indeed store and query JSON (not sure if Hasura supports that, though.)
But it seems that I can just use MongoDB first, and migrate later, if trouble comes?
BTW, what database in the backend for your GraphQL? Postgres? Also, do you write your resolvers, or use Hasura?
Lastly, is there an economical way to use NewSQL, like Spanner?
MongoDB is a great choice for database. It's open-source, has better support for NoSQL relationships and such than firestore, and I overall have liked working w/ it in the past. If you like it go for it!
I'm now rolling Hasura w/ Postgres as my database. I don't write resolvers I just use the CRUD operations that Hasura exposes. If I need to do something more complex I can use Hasura "Views" (which you might be interested in), so likely I won't need to write resolvers for a while (maybe ever).
Postgres has JSON storage which is a pretty great feature about it.
Never used NewSQL, sorry! I'll check it out though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I care about the price and monitoring as well.
Convince me to use SQL
Pacharapol Withayasakpunt ・ Aug 11 ・ 1 min read
It seems that NoSQL is better for denormalized, but RDBMS is better for normalized. Still, many RDBMS can indeed store and query JSON (not sure if Hasura supports that, though.)
But it seems that I can just use MongoDB first, and migrate later, if trouble comes?
BTW, what database in the backend for your GraphQL? Postgres? Also, do you write your resolvers, or use Hasura?
Lastly, is there an economical way to use NewSQL, like Spanner?
Good questions.
MongoDB is a great choice for database. It's open-source, has better support for NoSQL relationships and such than firestore, and I overall have liked working w/ it in the past. If you like it go for it!
I'm now rolling Hasura w/ Postgres as my database. I don't write resolvers I just use the CRUD operations that Hasura exposes. If I need to do something more complex I can use Hasura "Views" (which you might be interested in), so likely I won't need to write resolvers for a while (maybe ever).
Postgres has JSON storage which is a pretty great feature about it.
Never used NewSQL, sorry! I'll check it out though.