I'd like to discuss your thoughts on relational and non-relational databases (mainly) and their use cases. I'm more accustomed to fixed column schemas from relational dbs but I am considering switching to an alternative.
Here's an example schema where I'd want to consider speed and ease of access as keypoints:
Relational - One table for users, one table for the cars they own and one table with varying lengths of properties listed for each car. So the cars table would reference the user in the users table, and the properties would reference which car they belong to (all via unique id/key).
Non-Relational - Multiple ways of achieving this, but the most obvious to me would be an object for each user, which I can best describe or return in json, ie :
some other car...
Let's also assume there's 10000 users and each user has 5000 cars, and each car has 100-1000 props (yes they're very rich :D)
As far as I've read, the latter should be easier to change at any point, be simple to access and also offer similar speed.