6Bee

I would start with a local, ideally modular(i.e.:containerized) prototype before considering any financial commitments. Your DB choices will boil down to what your project does and what it needs to persist as it runs. Choose the simplest versions of the DB software, per use case. Postgres handles a lot of things and is super extensible, from transactions, data document(think JSON) storage, vector storage(Supabase is built atop Postgres). Majority of pubcloud vendors also have a managed Postgres offering, makes ramping up a bit easier. See how that works out for you locally, and slowly ramp up to hosted solutions. If you find yourself running thin/going a bit too far into the weeds for your comfort, a managed solution may help. All in all, start small & identify what your Go project needs to get done/saved. This will inform your DB choice more than anything we can suggest. Try not to rush into subscription services unless you're okay w/ spending money from a place of uncertainty