3 ms·
My backend setup for my one-person startup ("case study" for my book, https://opinionatedlaunch.com https://opinionatedlaunch.com) is GitHub (for code repo and
by wiradikusuma 2y ago
My backend setup for my one-person startup ("case study" for my book, https://opinionatedlaunch.com https://opinionatedlaunch.com) is GitHub (for code repo and CI/CD), Firebase (auth, analytics, push notif) and CloudFlare (static pages, DNS stuff) and Fly.io. Less work but more done.
My only complaint Fly.io doesn't have managed DB (https://fly.io/docs/postgres/getting-started/what-you-should-know/#fully-managed-postgres https://fly.io/docs/postgres/getting-started/what-you-should...) and task queue.
At work we use GCP, but try to be as high as possible in the abstraction layer (e.g. use Cloud Run and Cloud SQL).
- vindex10 2y agoI was able to use managed Postgres ~a year ago on Fly.io. They seem to have offloaded its maintenance to Supabase, but it is still seamlessly interfaced with Fly.io. Moreover, they still allow 1 free db per account: > Supabase offers one free, resource-limited database per Fly.io user Are you concerned that it is not directly managed by Fly.io? * also Kafka: https://fly.io/docs/reference/kafka/ https://fly.io/docs/reference/kafka/