Live data from Hacker News

Bye Bye Mongo, Hello Postgres

theguardian.com

21–30 of 427 posts

Re: Bye Bye Mongo, Hello Postgres

#21

They have some unique requirements to host within their own VPC. I just use mlab.

Define unique?

My company does bespoke software development for large enterprises. If they're on AWS having all your services within a VPC you control is something of table stakes for a lot of large company engineering and security teams.

Re: Bye Bye Mongo, Hello Postgres

#22
post #8

Earlier quoted context omitted.

They probably mean that they wanted the DB hosted within the private subnet of their VPC. With a traditional hosted offering you’d connect over the public net to a system hosted by the SaaS provider. With RDS they could spin up the DB within their own VPC.

Couldn't they do this by using Atlas and choosing AWS as the host?

Atlas runs tne hosts inside mongodbs AWS account, we have the same restriant, becuase of client privacy isses and gdpr compliance we can let a 3rd party host the data, amazon is ok beacuse we control tbe data on tbe instances.

Re: Bye Bye Mongo, Hello Postgres

#23
post #19

As a reminder, PostgreSQL is distributable under a license that's basically BSD/MIT: https://www.postgresql.org/about/licence/ MongoDB, on the other hand, recently changed their license to an abomination that many people think is no longer Free: https://news.ycombinator.com/item?id=18301116

Because there is no company behind PG, no one is loosing money if FANG get your app for free and build something around it. You should ask Redis, Grafana, Nginx ect ... if they're happy about super large company doing that kind of thing.

There are bunch of companies behind PG actually. From Fujitsu and EnterpriseDB to smaller ones like 2ndQuadrant, PostgresPro, CitusDB and many others.

Re: Bye Bye Mongo, Hello Postgres

#24
I never got around to using Mongo as my main doc db because it was incredibly hard to find a management tool.

I now use json supported functions in SQL Server and do not have the need for a different type of database. SQL Server handles my small 'documents db' implementation with the infrastructure of a RDMS. Win win for me.

To me Mongo just got popular by mistake way too early. It's like having a celebrity retweet your post because they liked what they saw at the time, exposing you to the world where everyone now thinks you have something important to say. Not surprisingly, you don't!

Re: Bye Bye Mongo, Hello Postgres

#25

They have some unique requirements to host within their own VPC. I just use mlab.

Define unique? My company does bespoke software development for large enterprises. If they're on AWS having all your services within a VPC you control is something of table stakes for a lot of large company engineering and security teams.

We are the same, atlas is a non-starter

Re: Bye Bye Mongo, Hello Postgres

#27
Did they ever publish the rationale for why they used MongoDB in the first place? They mention having 2.3 million content items. If we assume that they have 100 DB entries for each content item, that's still only 230 million DB items. In that case, was it important to run a sharded cluster vs a typical primary-secondary HA setup? (which they ended up switching to)

Re: Bye Bye Mongo, Hello Postgres

#29
post #5

Earlier quoted context omitted.

The way I read it, mongo was hosted the same way postgres was - on AWS VMs. OpsManager wanted to be more like a SaaS. I'm a little skeptical of the idea that you can do custom software development with a custom database schema and realistically expect to outsource DB management. But sure, you can try. And in any case, you'd hope a largely read-only and document oriented dataset like a newspaper's has a relatively sim…

Why wouldn’t you be able to outsource database server management? Are you referring to outsourcing schema management?

By server management - do you mean VM? Sure, you can outsource that. I mean that what and how a home-grown application uses a database tends to mean that database (software/schema/optimization/whatever) management cannot be application agnostic. So if you outsource this, you're either effectively hiring a consultant that still needs to deal with and learn details of specifically your application, or you should assume it's going to cost you some time to do yourself.

I'm sure you can get advice or buy know-how; but they're too coupled to think you're not also going to need to spend some time too. (At least: assuming your workload is large enough and complicated enough that naive brute force isn't an attractive option).

Re: Bye Bye Mongo, Hello Postgres

#30
The Guardian example was heavily used by MongoDB as a case study to pitch their database to others in 2011:

https://www.mongodb.com/customers/guardian

https://www.mongodb.com/presentations/mongodb-guardian

https://www.slideshare.net/tackers/why-we-chose-mongodb-for-...

And reupping my previous, three-part series on MongoDB:

On MongoDB

NoSQL databases were the future. MongoDB was the database for "modern" web engineers and used by countless startups. What happened?

https://www.nemil.com/mongo/index.html

Post reply on HN