Add support for FARM stack 🧑‍🌾

[nenb]

What problem are you trying to solve?

• Make it easy for full-stack developers, small organisations and MongoDB users in general to integrate SuperDuperDB into their FARM stack. I propose to use the acronym FARMS for this new stack.
• Provide examples of the types of problems and pain-points that SuperDuperDB can solve for full-stack developers.

Why should we solve it?

• We want to increase adoption of SuperDuperDB - we want to minimise the boring 'plumbing' that users may need to do to adopt SuperDuperDB, as this will harm adoption.
• We want to better understand the pain-points for full-stack developers when using our package.
• We should solve it now as we already have MongoDB integration, and are actively considering adopting FastAPI in our stack eg Re-allow pydantic 2.x #599. This means that the FARM stack overlaps quite well with our current expertise and the features offered by SuperDuperDB.

How do you propose to solve it?

• Develop a cookiecutter package for the FARM stack that also includes SuperDuperDB ie develop a FARMS cookiecutter.
• Develop and deploy (location TBD) several use-case apps that make use of the FARMS stack.

What other approaches did you consider?

• We could also consider adding support for the MEAN and MERN stacks. These stacks have greater adoption than the FARM stack. However, as these stacks don't overlap as well with our current expertise, they would likely require more work. (Note that this does not prevent adding support for these stacks at a later date!)

What could go wrong?

• FARM is specifically aimed at MongoDB users. As such, it is of limited/no-use to non-MongoDB users. This limits the amount of new users we can reach. To mitigate this risk, this proposal is strictly time-bounded - I propose 1 month from the beginning of the issue to completion of the work. (Note that this work will be in parallel with other work. I am proposing 1 month to allow some time to receive feedback from users and iterate on the initial use-cases a little.)

[rec]

I got a little sidetracked reading about this whole stack, very logical of course.

I love the acronym, we should for sure use it.

---

The job boils down to two tasks:

1. One or more small, interesting sample apps using SuperduperDB on the back end and React on the front end
2. The cookiecutter package

I think 2 is trivial if we can do 1.

I think 1 wouldn't be terribly hard if we had even one good idea that demonstrated sddb and had even a little React in it and wasn't very big.

I spent several minutes thinking about this, but no particularly thrilling idea came up. What are some existing projects that might do well with a little React front-end?

[kislerdm]

Great proposal, Nick! I feel that it's applicable beyond FARMS because clear instructions how to integrate SDDB, or scaffolding/instrumentation (cookiecutter) will be appreciated and used by all our users.

[rec]

Since then I've realized that a couple of FARMS demos would also fill a need I have when I'm explaining this to people - they want to see some webpage that "does the thing".

The key missing part is the actual demo application we would pick.