You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 16, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 16, 2021. It is now read-only.
When MongoDB changed their license it made the case for us operating it, for the Helm Hub, to need to use something else. We can't use the newer versions, or so I'm told.
I would suggest replacing MongoDB with PostgreSQL. It now can handle documents and, if I understand what I read right, it's the foundation for the MongoDB API compliant service that Amazon operates.
In any case, the idea is to use a data store whose license we can and with versions getting updates for security and bugs.
Why exactly is that? As far as I know projects using MongoDB, on any version, including the latest, is completely allowed. Effectively blocking any new release (helm/hub#212) seems unnecessary.
Activity
nwmac commentedon Jun 25, 2019
@mattfarina We are interested on using Monocular on the SUSE Stratos project (https://github.com/SUSE/stratos), but also can not use MongoDB due to the license change.
Would you consider refactoring Monocular to have a data-store abstraction layer under which different back-end repositories could be implemented?
Also, have you considered FoundationDB DocumentDB layer (https://www.foundationdb.org/blog/announcing-document-layer/)? Its Apache 2 licensed and offers API compatibility with MongoDB.
mattfarina commentedon Aug 8, 2019
@nwmac We would consider FoundationDB
dhrp commentedon Mar 31, 2020
Just jumping in; but
Why exactly is that? As far as I know projects using MongoDB, on any version, including the latest, is completely allowed. Effectively blocking any new release (helm/hub#212) seems unnecessary.