Live data from Hacker News

Homebrew removes MongoDB from core formulas

github.com

151–160 of 291 posts

Re: Homebrew removes MongoDB from core formulas

#151

Earlier quoted context omitted.

A lot of companies got lured into using mongodb because it was so developer friendly. It cost nothing and it was easy bring in the back door and alleviated the need for thought. Then their sales people started coming around and asking for insane sums of money (like $10,000 per instance per year plus 100% markup on hardware to run in AWS - support is extra). They were worried about amazon and others offering a better…

Maybe I'm misunderstanding, but I thought the new license is just about offering MongoDB as a service by itself. But if you're making any other sort of website and use MongoDB as a database, you can still install it and use it for free. If the companies got lured into using MongoDB as a service, then I understand that prices could increase and companies could be in a pickle. But if companies got lured into using Mong…

The fact that mongo was willing to screw over one set of users makes me worry they'd be willing to screw over all their users. It's a risk I wouldn't take, especially when there are so many other (arguably better) options out there.

Re: Homebrew removes MongoDB from core formulas

#152
post #93

Earlier quoted context omitted.

You can make a simple HTTP/1.1 server in 200 lines of good C. Not one that runs HTTP/3.0 including QUIC and TLS.

HTTP 3 isn't even in production yet.

Define production and define HTTP3. The beauty of open source is that you can be already serving pages using QUIC and TLS1.3 while the standard is being finalised.

Re: Homebrew removes MongoDB from core formulas

#153
post #142

Earlier quoted context omitted.

A lot of companies got lured into using mongodb because it was so developer friendly. It cost nothing and it was easy bring in the back door and alleviated the need for thought. Then their sales people started coming around and asking for insane sums of money (like $10,000 per instance per year plus 100% markup on hardware to run in AWS - support is extra). They were worried about amazon and others offering a better…

> If it had been SQL it would have been easy to drop in another database. Not true at all. Way too many organisations are locked into Oracle just because it's too hard to switch to something cheaper.

Why is this? If Oracle uses SQL why can you not just export the database, make some transformations, and import it into a PostgreSQL db for example?

Re: Homebrew removes MongoDB from core formulas

#154
post #142

Earlier quoted context omitted.

A lot of companies got lured into using mongodb because it was so developer friendly. It cost nothing and it was easy bring in the back door and alleviated the need for thought. Then their sales people started coming around and asking for insane sums of money (like $10,000 per instance per year plus 100% markup on hardware to run in AWS - support is extra). They were worried about amazon and others offering a better…

> If it had been SQL it would have been easy to drop in another database. Not true at all. Way too many organisations are locked into Oracle just because it's too hard to switch to something cheaper.

Including Amazon, until recently.

Re: Homebrew removes MongoDB from core formulas

#155
post #94

Earlier quoted context omitted.

So why not just use a RDMS from day one?

A lot of people have difficulty trying to organize complex hierarchical data into rows and columns. A lot of places make you go through a dba to create or change a database which rubs power users the wrong way - and admittedly most of the dbas I’ve worked with are a lot more concerned with making backups fast then in your applications performance. Mongodb doesn’t make you do any of that. It doesn’t make you have auth…

Database versioning and migrations are a pain. I’ve tried both home grown and commercial database systems to make database changes part of the CI/CD process. I haven’t found one that I liked.

When I did implement a system with C#/Mongo, I fell in love with changing my database schema just by changing my C# objects. With the C# driver you can include a Dictionary as part of your object to round trip unmapped fields.

Not to mention that after you go through all of your modeling and figuring out your aggregate roots, you can just store the entire object graph with one .Add and the entire object is stored atomically without having to worry about transactions, table locks, etc.

Unlike with an RDMS where your beautiful aggregate root has to constantly be composed and decomposed.

Re: Homebrew removes MongoDB from core formulas

#158
post #142

Earlier quoted context omitted.

> If it had been SQL it would have been easy to drop in another database. Not true at all. Way too many organisations are locked into Oracle just because it's too hard to switch to something cheaper.

Why is this? If Oracle uses SQL why can you not just export the database, make some transformations, and import it into a PostgreSQL db for example?

Because Oracle uses Oracle's flavour of SQL, and no two databases are feature compatible.

Re: Homebrew removes MongoDB from core formulas

#159
post #142

Earlier quoted context omitted.

> If it had been SQL it would have been easy to drop in another database. Not true at all. Way too many organisations are locked into Oracle just because it's too hard to switch to something cheaper.

Why is this? If Oracle uses SQL why can you not just export the database, make some transformations, and import it into a PostgreSQL db for example?

If you are correct then your consultancy can stand to make hundreds of millions and save companies billions on their Oracle instances!

More likely, though, is that Oracle users use Oracle-specific flavors of SQL in lots of legacy apps that no one wants to touch, and rely on the support contracts for continued assistance in keeping the database performant for its query load.

Re: Homebrew removes MongoDB from core formulas

#160
post #142

Earlier quoted context omitted.

> If it had been SQL it would have been easy to drop in another database. Not true at all. Way too many organisations are locked into Oracle just because it's too hard to switch to something cheaper.

Why is this? If Oracle uses SQL why can you not just export the database, make some transformations, and import it into a PostgreSQL db for example?

[deleted]
Post reply on HN