Today we’re announcing the private beta of Fly Managed MySQL. Please sign up to our waitlist. We’ll send invites as soon as possible. We need your feedback!
So, we’ve been furiously hacking away at our own, Fly-managed database services. You may have noticed our recent improvements to Fly Postgres and Fly Kubernetes. These updates were part of the drive towards managed databases.
I don’t know if this is in the cards, but what I most want is a pay-as-you-go pricing model with no floor. Charge whatever is reasonable per GB of storage, number of queries, etc., but for example, I don’t like Supabase’s pricing model of free for 500MB, but 501MB costs $25/mo.
A small side question about postgres you mentioned in your post. Is now supabase going to be the managed database service for fly or are you pushing more updates to bring the postgres-flex system to a managed database service. Would be great to know!
It would be ideal if replicas didn’t have to use the same instance type as the primary. I’d like to allocate a more powerful instance (better CPU, more RAM) for the primary since it handles most of the workload, and use cheaper instances for the replicas. In the event of a failover, the replica instance could be upgraded to match the primary’s specs.