Ask HN: Posgresql JSON or MongoDB?
21–26 of 26 posts
Re: Ask HN: Posgresql JSON or MongoDB?
#22I'm also curious if anyone has tried JSON types in Amazon PG compatible Aurora or RDS?
We have been using JSON on RDS extensively since 9.5. Today probably 80%+ of PG JSON capabilities are used by the app in some way for some pretty complex use-cases (fintech). Never had any issues with this on RDS - everything just works (multi-as, read replicas, performance profiling etc) and we love it. Haven't tested Aurora yet.
It seems cockroachdb, aurora and cosmos are targeting similar use cases.
Re: Ask HN: Posgresql JSON or MongoDB?
#23Earlier quoted context omitted.
what about High Availability?
Just use Amazon RDS and let them deal with it. None of the theoretical scaling benefits of Mongo outweigh the clusterfuck of maintenance, data inconsistency, and other general problems that shitty, shitty piece of software has.
I didnt mind mongo in a couple of my previous jobs. We never noticed data issues and we did some crazy things like generating mongologs on one machine and moving them to another manually .
Re: Ask HN: Posgresql JSON or MongoDB?
#24Re: Ask HN: Posgresql JSON or MongoDB?
#25Earlier quoted context omitted.
We have been using JSON on RDS extensively since 9.5. Today probably 80%+ of PG JSON capabilities are used by the app in some way for some pretty complex use-cases (fintech). Never had any issues with this on RDS - everything just works (multi-as, read replicas, performance profiling etc) and we love it. Haven't tested Aurora yet.
Ok you've been using postgres RDS? Im mostly interested in Aurora. It seems cockroachdb, aurora and cosmos are targeting similar use cases.
IMO RDS is perfect for most use-cases. I'd strongly encourage to try it out - it's highly performant and very reliable (uhhh... well...). Aurora has a significant edge under very significant loads (i.e. >300 concurrent clients), but can be slower under typical scenarios (0-100 concurrency).