Fellow blinders, are there any good resources to get a good handle on how to do data modelling for SQL vs NOSQL database? I've been using Grokking the system design for an upcoming TPM interview at Google and am confused. 1. Design instagram section of the resource shows 2 tables ( Photo, User) for SQL, and then, it says "if we go with NOSQL, we also need 'UserPhoto' and 'userFollow'...My question is do you need all 4 tables for NOSQL or just the last two? It seems the last two suffice. 2. Unless there are ACID transactions, it seems you can almost invariably go with NoSQL database for distributed systems -true? In my early 40s, Master's in EE, and toddler in CS :) Trying to make a 180 degree turn for a career in tech. YOE: 10 TC : 117K #software #swe #tpm
If you are to simplify things, then in general, you can go with NoSQL if you don't need ACID, since that's one of the main considerations why ppl chose SQL over it. You can read up more at https://nodeflair.com/blog/sql-vs-nosql-databases-system-design-interview
Have you started with basic data modeling concepts. It is not about creating tables and columns.