Re:Amazon RDS for PostgreSQL
by e12e on Friday November 15, 2013 @12:16PM
(#6740623)
I'd venture a guess, and say that Postgresql didn't win, sqlite and mongodb won. I think a lot of the reason behind MySQLs initial success was blogs and various php-apps that weren't architected properly (from a db perspective). Some of these didn't need a ("proper") db, and most of them probably did, but "worked well enough" without one.
I never really understood why you'd want to use a separate dbms if it couldn't do proper constraints, triggers, transactions and materialized views for you -- then it starts to feel like a lot of wasted effort.
So for many of the use-cases where MySQL might have been appropriate, we now have sqlite, mongodb, memcache/redis and a few others.
Personally I don't really see any reasonable use-cases for mongodb, just as I didn't see many reasonable use-cases for mysql -- not that you couldn't build stuff on top of it, just that it wasn't a very good idea.
I never really understood why you'd want to use a separate dbms if it couldn't do proper constraints, triggers, transactions and materialized views for you -- then it starts to feel like a lot of wasted effort.
So for many of the use-cases where MySQL might have been appropriate, we now have sqlite, mongodb, memcache/redis and a few others.
Personally I don't really see any reasonable use-cases for mongodb, just as I didn't see many reasonable use-cases for mysql -- not that you couldn't build stuff on top of it, just that it wasn't a very good idea.