Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FerretDB: open-source MongoDB alternative

blog.ferretdb.io

Post reply on HN
Print view View original

111–120 of 130 posts

Re: FerretDB: open-source MongoDB alternative

#111

Post by that_guy_iain »

PeterZaitsev wrote: post #95
that_guy_iain wrote: post #65

Earlier quoted context omitted.

AGPL is basically the same thing, except far more reaching. AGPL, to my understanding, makes it a requirement if you allow people to use the software via network levels. “Program as a Service” seems a lot more limited in scope. All new licenses come with risk since the decisions can only be made via court decisions.

Well, AGPL did no allow to create Monopoly in practice - Compose.io, ObjectRocket and others could offer alternatives to MongoDB Atlas without any permission. This was benefit for users but obviously not something classical corporaton would enjoy

It was a benefit for classical corporations not users. These companies can still create alternatives. It’s just they’re forced to share how they did it. It’s that forcing of sharing which is at the heart of GPL.

Re: FerretDB: open-source MongoDB alternative

#112

Post by that_guy_iain »

zokier wrote: post #61
that_guy_iain wrote: post #54

Earlier quoted context omitted.

Those aren’t listed are they? The idea you need to release code for the os, file system, network routers, etc is absurd.

SSPL license text doesn't set any limits on the scope for source release. Verbatim quote: > “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation…

Your interpretation ignores the sentence “all such that a user could run an instance of the service using the service source code”. That just means they need to be able to run the service. Not have the exact same stack.

Re: FerretDB: open-source MongoDB alternative

#115

Post by eropple »

solatic wrote: post #93
eropple wrote: post #27

Earlier quoted context omitted.

If you aren't normalizing, how are you ensuring that you don't avoid anomalies?

Proper NoSQL design has a different perspective, it asks you "well, so what if you have an anomaly?". One example could be movies, with actors, producers, genres, etc. that could all be in separate tables in a relational database, or each movie could be a document in a document database. Now let's imagine that an actor changes their name a few years after the movie is released. Is it important to go back and change t…

That makes sense. I tend to go away from non-relational models for this reason, but it's definitely a matter of risk management.

Re: FerretDB: open-source MongoDB alternative

#117

Post by aleksi »

CodesInChaos wrote: post #107
peterfarkas wrote: post #48

Earlier quoted context omitted.

Yes, FerretDB is a layer which implements the MongoDB wire protocol on top of Postgres. Right now we are using JSONB, but this affects performance and we need to depart from this strategy in the long run. We have an article which explains the concept [1]. I wouldn't go into the document vs. relational argument, all arguments for and against would have merit. There are valid use cases for document databases (take e-co…

> we need to depart from this strategy in the long run What's the alternative you want to move to?

Probably a custom PostgreSQL extension for BSON support.

The biggest issue right now is that MongoDB compares and sorts values differently than PostgreSQL/jsonb. For that reason, we have to do a lot of filtering on the FerretDB side, and that can't be great for performance. Pushing more work on the database size should make FerretDB perform much better.

Re: FerretDB: open-source MongoDB alternative

#118

Post by aleksi »

yawnxyz wrote: post #76
peterfarkas wrote: post #48

Earlier quoted context omitted.

Yes, FerretDB is a layer which implements the MongoDB wire protocol on top of Postgres. Right now we are using JSONB, but this affects performance and we need to depart from this strategy in the long run. We have an article which explains the concept [1]. I wouldn't go into the document vs. relational argument, all arguments for and against would have merit. There are valid use cases for document databases (take e-co…

if we use Ferret for prototyping and eventually land on a schema, would it be possible to convert the FerretDB rows into more structured postgres? Would be so cool if it could just analyze and create a schema for you, you double check it, and it just works. I think being able to convert back and forth would make it so worthwhile!

Yeah, we want to do that: https://github.com/FerretDB/FerretDB/issues/226

Re: FerretDB: open-source MongoDB alternative

#119

Post by aleksi »

exabrial wrote: post #116

Somewhere there's an actual implementation that copies everything to /dev/null, with the justification that if you're using mongodb, you probably don't care about your data anyway. Can't seem to find it.

I think you mean https://github.com/dcramer/mangodb

Re: FerretDB: open-source MongoDB alternative

#120

Post by that_guy_iain »

aleksi wrote: post #99
that_guy_iain wrote: post #65

Earlier quoted context omitted.

AGPL is basically the same thing, except far more reaching. AGPL, to my understanding, makes it a requirement if you allow people to use the software via network levels. “Program as a Service” seems a lot more limited in scope. All new licenses come with risk since the decisions can only be made via court decisions.

> AGPL, to my understanding, makes it a requirement if you allow people to use the software via network levels. AGPL requirements do not trigger if you don't modify the source code. The relevant text is in section 13: > […] if you modify the Program, your modified version must prominently offer all users […] See also [1], [2], [3]. > “Program as a Service” seems a lot more limited in scope. AGPL scope: > The "Corresp…

> As noted in another thread, that's not only beyond the scope of the software itself – it is beyond the scope you _can_ relicense and arguably beyond the scope of the copyright terms themselves.

This is not true. People who are saying this would have said this about GPL when it first came out.

Post reply on HN