We just switched on Managed Upstash Redis, a private, Redis compatible database, via our partnership with the admirable team at Upstash. You can deploy Upstash Redis today in any Fly region, both as a primary and a read-only replica. Give it a try with:
flyctl redis create
We want your feedback!
A Few Interesting Details
Upstash Redis on Fly is different than some other Redis offerings you’ll find in the wild. Check all the details in the docs. Briefly:
Your database is not exposed to the public internet! Each database is deployed on Fly infrastructure. It’s visible to your entire Fly organization via a private IPv6 address that routes traffic to the geographically nearest replica (or primary).
When using read replicas, you can use a single connection URL for all your app instances. Writes are automatically forwarded by Upstash Redis to the primary.
Upstash Redis is compatible with the Redis API, but isn’t stock Redis. Check their docs for details on supported commands.
Managed Services on Fly
We’re trying something new at Fly. Customers want managed services. But running managed services is a whole business in itself. And using internet-exposed services on other platforms, from Fly apps, has its downsides: potential latency in distant regions, exposure to attacks, and so on.
A happy middle path: providers provision services on Fly, for Fly customers. We’ve been working on plumbing to make this happen, like the Machines API and Flycast private load balancing. This gives providers just enough power to tightly control their deployments, and to expose their services to customers in a simple, secure fashion (and vice-versa).
Your feedback will help us figure out how upcoming integrations will work.
Thanks for your time.
