Hacker News new | ask | show | jobs
by fnord123 3547 days ago
Most end users of databases don't change the code so they're not on the hook for releasing changes to the source. And if they did, it gets slightly muddy since the presence of even a load balancer may mean that users aren't connecting to the database itself and hence aren't entitled to access changes to the source.
1 comments

The main issue is that most companies won't spend the time or money to do a full legal analysis and simply don't allow AGPL to be used in projects.
I agree. I think the AGPL license perceived risk played a significant role in RethinkDB's lack of user acceptance.
Can you explain your reasonings as to why you believe this? Also, can you explain how this perceived risk didn't apply to other products such as MongoDB?
I know of several fortune 500 companies that blanket ban AGPL. It's not just about the intent of the license. These multi million dollar lawyers can not agree beyond a shadow of a doubt AGPL is safe.
I would half seriously posit that people who are using MongoDB in their software are not really all that risk-averse in the first place