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
I believe FerretDB aims to closely follow the MongoDB specification, positioning itself as a drop-in replacement for MongoDB. In contrast, DocumentDB appears to be pursuing a broader vision; defining the future of open-source document databases.
As far as I understand, DocumentDB plans to evolve its own specification over time, gradually diverging from MongoDB’s model and by extension, from FerretDB as well.
Based on this perspective, I feel that having both databases in the ecosystem could make sense : each serving different needs and contributing uniquely to the future of document-oriented data.
It is still very much a wish to have DocumentDB as a native Cozystack Database‑as‑a‑Service option.
From what I can see, the DocumentDB project continues to receive active and consistent contributions over time, whereas FerretDB seems to have slowed down in recent months. In addition, FerretDB is not fully up to date with the latest underlying DocumentDB releases (since FerretDB relies on DocumentDB internally), which creates a growing gap.
For these reasons, support for DocumentDB directly within Cozystack remains relevant and desirable. Its development pace and long‑term vision make it a strong candidate for a first‑class integration.
Timofei Larkin (@lllamnyp) The user still considers native DocumentDB support in Cozystack important due to its active development and long-term vision, noting FerretDB's slower pace and lag in updates. Could you please assist with this request?
Hi, YohanS (@YohanSciubukgian). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary
You opened this issue to request native DocumentDB support in Cozystack as a supported database option alongside FerretDB.
In the discussion, Andrei Kvapil (@kvaps) asked whether DocumentDB should replace FerretDB or remain a distinct option due to compatibility differences.
You clarified that FerretDB is intended as a MongoDB drop-in replacement, while DocumentDB is developing a broader specification and long-term vision.
You later reiterated that DocumentDB remains a desirable first-class DaaS option because of its active development and direction.
The issue has since seen no recent activity and was previously flagged stale by automation.
Next Steps
If this is still relevant on the latest version of the cozystack repository, please comment to keep the discussion open.
Otherwise, this issue will be automatically closed in 7 days.
A new database app needs a proposal first. Could you open one in cozystack/community? It should say which engine is behind it (FerretDB on Postgres or something else) and who maintains the operator.
Activity
kvaps commentedon Oct 31, 2025
Interesting, should we consider replacing FerretDB by DocumentDB or it is not fully compatible?
YohanSciubukgian commentedon Nov 3, 2025
I believe FerretDB aims to closely follow the MongoDB specification, positioning itself as a drop-in replacement for MongoDB. In contrast, DocumentDB appears to be pursuing a broader vision; defining the future of open-source document databases.
As far as I understand, DocumentDB plans to evolve its own specification over time, gradually diverging from MongoDB’s model and by extension, from FerretDB as well.
Based on this perspective, I feel that having both databases in the ecosystem could make sense : each serving different needs and contributing uniquely to the future of document-oriented data.
dosubot commentedon Feb 2, 2026
Hi, YohanS (@YohanSciubukgian). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
YohanSciubukgian commentedon Feb 2, 2026
It is still very much a wish to have DocumentDB as a native Cozystack Database‑as‑a‑Service option.
From what I can see, the DocumentDB project continues to receive active and consistent contributions over time, whereas FerretDB seems to have slowed down in recent months. In addition, FerretDB is not fully up to date with the latest underlying DocumentDB releases (since FerretDB relies on DocumentDB internally), which creates a growing gap.
For these reasons, support for DocumentDB directly within Cozystack remains relevant and desirable. Its development pace and long‑term vision make it a strong candidate for a first‑class integration.
dosubot commentedon Feb 2, 2026
Timofei Larkin (@lllamnyp) The user still considers native DocumentDB support in Cozystack important due to its active development and long-term vision, noting FerretDB's slower pace and lag in updates. Could you please assist with this request?
github-actions commentedon May 2, 2026
This issue has had no activity for 60 days and was marked
lifecycle/stale.It will be closed in 14 days unless commented or labelled
lifecycle/frozen.dosubot commentedon Aug 1, 2026
Hi, YohanS (@YohanSciubukgian). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary
Next Steps
Thanks for your understanding and contribution.
lexfrei commentedon Sep 23, 2026
A new database app needs a proposal first. Could you open one in cozystack/community? It should say which engine is behind it (FerretDB on Postgres or something else) and who maintains the operator.