Decide on our (initial) infrastructure stack

[nenb]

What problem are you trying to solve?

• In the first few months of the project our technical focus will largely be on improving and developing the SuperDuperDB package. Deciding now on an infrastructure stack (for these initial months) that is simple and easy to use will allow us to dedicate our focus to the SuperDuperDB package.
• Understand what it is like for our users when they deploy SuperDuperDB on popular infrastructure stacks

Why should we solve it?

• Increase the amount of time we have to improve SuperDuperDB features and functionality.
• Understand how SuperDuperDB behaves when deployed with a stack that is popular with our users.

How do you propose to solve it?

• MongoDB Atlas (MongoDB service)
• Fly.io (Platform to host and monitor app)
• GitHub packages (External storage, build platform)
• S3 (External Storage)

What other approaches did you consider?

The following are other options that we may wish to also consider:

• Vercel
• Cloudflare
• Azure Blob
• GCP
• AWS Lambda