Dear FA team,
Let me start by saying, that I am a big fan of the new
The new ways of (1) hooks, (2) replication strategies, and (3) magically transforming nested objects in the data model to new collections, really turn your tool into a Swiss army knife for back office operations. Our startup, Jurata, is a legal marketplace, that combines many 3rd-party tools (Stripe, Bexio, HubSpot, MongoDB, etc.) in order to have our operators manage long user journeys, as well as deploy rather complicated reporting. Being able to deal with all of this in a concentrated Typescript codebase (sorry, DHH) and minimal configuration effort makes the life of our small tech team considerably better. But it’s more than DX: now we might soon be able to offer quick and stable answers to the exacerbated feature requests of our operations team without needing to enter the dark realm of enterprise software.
Thank you for your excellent work - we are witnessing a powerful product vision being deployed here. I have and probably still will make multiple bug reports and feature requests in order to push and migrate your new library to our production environment. Please, take it as a compliment and forgive my sense of urgency.
So, here we go: I saw that the
cacheInto feature for the replication strategy supports an SQL database according to the documentation. Are there any plans of supporting Mongoose as a caching database? If yes, do you have any idea about a rough non-committing timeline? I need to decide, whether to build additional infra for our separate SQL DB on our cloud environment - which would not be necessary if I can just use mongoose.