> These PostgreSQL features are relatively recent. The jsonb column type dates back to 9.4, which was released in Dec 2014, less than three years ago. MongoDB had been around for well over five years by that point.
It's much much harder to design a reliable engine than a new datatype.
> There are few applications that need distributed scalability beyond what PostgreSQL can provide, but I'd argue that it's not uncommon to have problems with Oracle scalability, if you don't have deep pockets for licensing.
Yes they are, but chances are you don't have that need. You're not Google or Facebook.
You also picked up a really bad database to talk about scalability[1]
[1] https://www.datastax.com/wp-content/themes/datastax-2014-08/...
Re:Why Did So Many Startups Choose MongoDB?
by matthewrudy on Thursday July 06, 2017 @02:38PM
(#14712755)
Postgres had hstore for a few years before that which solved similar use cases, but was only key value (no nested objects)
Re:Why Did So Many Startups Choose MongoDB?
by s_kilk on Thursday July 06, 2017 @02:51PM
(#14712870)
Plus, hstore can only handle strings, so it's actually pretty bad when weighed up against a json-store
Re:Why Did So Many Startups Choose MongoDB?
by rhinoceraptor on Thursday July 06, 2017 @02:53PM
(#14712885)
Yep, you can't do stuff like update JSON in place until PG 9.5 (without resorting to a crazy regex, that is).
You also do have to think at least a little about your JSON structure given you can't really use an ORM to query JSONB, and the syntax for JSONB is a bit awkward at times.
There are few applications that need distributed scalability beyond what PostgreSQL can provide, but I'd argue that it's not uncommon to have problems with Oracle scalability, if you don't have deep pockets for licensing.