Joao Malcata

Hi Abdu-zeyad,

This is more about the use case and less about the tech you have experience with or that is trendy. Using a basic metaphor, SQL databases are trousers and NoSQL are shorts. If it is a warm and sunny day and you are going to the beach then you should wear shorts. If you are going to a formal wedding you have to wear trousers.

Sorry for that weird moment, going back to the tech question:

• Use cases where you have structured data with relations and transactions, and size is not huge (100M+) you should use SQL, like PostreSQL or Cloud Spanner.

• Use cases where you store semi-structured data, like json records, need fast writes, high volume, being eventually consisted is not an issue and you do not need complex operations like joins, subquery filtering, etc you should use a noSQL option like Firestore.

Also, there are a lot of different types of NoSQL architectures for specific use cases.

You are right, Paolo, object-oriented languages, ORM and SQL databases sit well together. PostgreSQL is the usual choice just because at a certain point in time it became the most successful open source SQL database. Before it was bought, a long time ago, I would have used MySQL instead.