Administered by:
#FerretDB 1.0 has been announced
Ferret is a proxy that sits between your #mongodb drivers & a #postgres db converting mongo queries into postgres SQL and using PG for the persistence.
I am finding myself at a complete loss as to any practical reason why someone would want to use this. The ONLY case i can make for it is that it satisfies people who are zealous about open source licenses and aren't happy with Mongo's.
What am i missing?
@masukomi
portability? stable API?
SQL access to data?
specialized backend db indexes? like #postgres #vectors or #postgis or #postgrest
@hobs this make take a couple toots. Please know that i'm honestly trying to work through the problem to understanding. I'm not trying to say "you're wrong". Going step by step through your points.
1. portability
How is this portable? You couldn't swap out PG for something else. I guess it'd let you port a Mongo centric codebase to PG but ...why would you want to?
2. stable api
the "stable api" is mongo's API so... switching to not-mongo is either no change or introducing risk
1/?
@masukomi
I don't use #mongo regularly, just #jsonb in #pg, so I'm guessing:
1. Mongo users could port data into pg using existing #backup & #recovery infrastructure, then they'd have both SQL and mongo query/dump/load options for future #migrations
2. The pg API will lag mongo's and sunset existing features later. And #SQL api as a fallback
3. A mongo app could transition to pg incrementally or partially, increasing maintainability by using mongo queries and SQL queries where they make sense