I don't know if I'm interpreting "movement" correctly, but I remember when NoSQL was super-hyped, then we realized that good ol' relational databases were still the best for most of the tasks.
Oh I'm with you. If I ever need to save unstructured data, I would just use JSONB inside of PostGres. Now I'm a type-safety kind of guy, so I'm not sure I ever would do that. But if I found a good use case, PostGres' JSONB is the tech I would use instead of MongoDb.
How is the name of that product supposed to be pronounced? Why is there only one S if it is both Postgres and SQL? FWIW I call it Post-GRE-SQL because somehow it seems "graduate level."
Originally the product was called "Postgres" (as Post Ingres, a DB at the time), then they joined the word SQL to make it clear it was a relational DB.
I think "POST-GRES-QL" is the correct one, like if it was "Postgres query language"
Depends your traffic profile and pockets. If your traffic follows a nice and constant increase/decrease pattern it's fine. If you have huge sudden spikes like we do...the only option is to turn it to on demand charging ...which is slightly more expensive but you don't have all the problems that come with bursting capacity, throttling and scaling.
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 don't know if I'm interpreting "movement" correctly, but I remember when NoSQL was super-hyped, then we realized that good ol' relational databases were still the best for most of the tasks.
I wasted a lot of time fretting about databases at that point.
8 years of MongoDB development here and I can confidently say that I will never recommend NoSQL for another professional project.
Nowadays, we are putting our JSON into relational databases :D
SCNR
Oh I'm with you. If I ever need to save unstructured data, I would just use JSONB inside of PostGres. Now I'm a type-safety kind of guy, so I'm not sure I ever would do that. But if I found a good use case, PostGres' JSONB is the tech I would use instead of MongoDb.
If you tell nobody, I am using postgres too 😉
How is the name of that product supposed to be pronounced? Why is there only one S if it is both Postgres and SQL? FWIW I call it Post-GRE-SQL because somehow it seems "graduate level."
Originally the product was called "Postgres" (as Post Ingres, a DB at the time), then they joined the word SQL to make it clear it was a relational DB.
I think "POST-GRES-QL" is the correct one, like if it was "Postgres query language"
After two years of using dynamodb I would gladly slap the team that came up with it. Especially the throttling mechanism
Is it bad?
Depends your traffic profile and pockets. If your traffic follows a nice and constant increase/decrease pattern it's fine. If you have huge sudden spikes like we do...the only option is to turn it to on demand charging ...which is slightly more expensive but you don't have all the problems that come with bursting capacity, throttling and scaling.