I see,
I'd recommend either:
- @cloudflare.social workers, at about $5 p/m you'd likely have everything hosted within the included limits with no overage needed yet. e.g. host api with workers, D1 sql for DB, R2 for asset storage + make heavy use of the free Cache API in the worker
or,
1/2
I'd recommend either:
- @cloudflare.social workers, at about $5 p/m you'd likely have everything hosted within the included limits with no overage needed yet. e.g. host api with workers, D1 sql for DB, R2 for asset storage + make heavy use of the free Cache API in the worker
or,
1/2
Comments
I project I did would have cost around $7k p/m on GCP, self host through hetzner ~$300p/m - this was hundreds of cores and ram - which you won't need
Serverless gives you low initial cost until your product scales, migration from that to serverful at a later date would be more time consuming
However serverful to serverful would be lift & shift with dns changes
I still favour convenience of not self-hosting when the cost is low or it will always fall into the free or low tier of a provider like Cloudflare
@bun.sh if self hosting to build the api, @coolify.io to run on the servers, postgres, clickhouse or sqlite for DB depending on what im doing, Redis for caching, jobs queues etc