[HN Gopher] Fly Postgres, Managed by Supabase
       ___________________________________________________________________
        
       Fly Postgres, Managed by Supabase
        
       Author : samwillis
       Score  : 80 points
       Date   : 2023-12-15 11:52 UTC (11 hours ago)
        
 (HTM) web link (supabase.com)
 (TXT) w3m dump (supabase.com)
        
       | biorach wrote:
       | Excellent news
        
       | kiwicopple wrote:
       | hey hn, supabase ceo here
       | 
       | Fly's current Postgres offering is unmanaged, so we're working
       | with them to run their managed offering. This is the same model
       | that they run with the Upstash team for Fly Redis[0]
       | 
       | We're still working with testers to roll out HA features. We
       | don't have firm timelines yet unfortunately, but we'll work with
       | the Fly team to make it happen as soon as possible
       | 
       | I'll stick around for any questions/comments
       | 
       | [0] Redis: https://fly.io/docs/reference/redis/
        
         | denysvitali wrote:
         | Two awesome technologies / companies joining forces!
         | 
         | Supabase and Fly.io are awesome - can't wait to see how cool
         | they can get together!
        
         | adam_gyroscope wrote:
         | Nice job & congrats!
        
         | pplante wrote:
         | You used the lowercase, it's cool we're all friends here in
         | your intro. Then reverted to correct casing for the remainder.
         | Disarmed everyone with that sly move.
         | 
         | nice touch!
        
           | saintfire wrote:
           | It is sort of funny that such an innocuous thing was all I
           | could think about while reading it.
        
       | jsierles wrote:
       | Joshua from the Fly.io side here, happy to answer any questions
       | about this integration.
        
         | nicoburns wrote:
         | Very excited for this. Aside from general reliability concerns
         | (esp. around deploys - not helped by cryptic failure messages).
         | Lack of managed Postgres has been the main thing keeping me off
         | fly (I use it for a couple of side projects, but nothing big
         | yet). And blob storage would probably be next on my list
         | (basically stateful things are the things I want managed) so
         | also excited to see that's being worked on.
         | 
         | Do you have any details on pricing (for this new postgres
         | offering) yet?
        
       | philip1209 wrote:
       | I'm excited to switch to this - I've been building Booklet on
       | Fly.io and their Postgres to make the app distributed [1]. The
       | biggest problem for me has been the Fly postgres configuration.
       | Specifically, Fly puts HAProxy in front of Postgres with a 30m
       | connection timeout [2], which keeps killing connections. This
       | should be manageable, but I'm seeing quirks in the connection
       | terminations that don't seem to align with their docs and keep
       | causing instability.
       | 
       | Question for the team members here - will the new PG still have
       | the same HAProxy in front?
       | 
       | [1] https://www.contraption.co/essays/booklet-architecture/
       | 
       | [2] https://community.fly.io/t/postgresql-connection-issues-
       | have...
        
       | plondon514 wrote:
       | Very excited about this. We're currently running a large db on
       | fly and looking for a managed pg. We're a fully Elixir shop and
       | this couldn't have come at a better time. Congrats to both teams!
        
       | candiddevmike wrote:
       | Where's the SLA?
        
       | nextworddev wrote:
       | I heard Supabase has known to have scaling issues beyond
       | prototype projects, can anyone comment who has production
       | experience with it?
        
         | tmountain wrote:
         | It's Postgres running on AWS, so it should scale as well as one
         | would expect with that combination. What issues are you
         | referring to specifically?
        
       | leros wrote:
       | I understand the neatness of fly.io's distributed VMs. Can
       | someone explain how Fly Postgres is different than a traditional
       | managed Postgres on something like Heroku.
        
         | tptacek wrote:
         | We wrote a blog post about this:
         | 
         | https://fly.io/blog/how-we-built-fly-postgres/
        
           | leros wrote:
           | If I'm understanding correctly, Fly Postgres isn't too
           | different from something like Postgres on Heroku? It's a
           | single instance/cluster in a single location.
        
       | smallerfish wrote:
       | Very nice. I've never really liked Supabase's network
       | restrictions setup
       | (https://supabase.com/docs/guides/platform/network-
       | restrictio...), and IIRC when I looked at it there was some weird
       | issue exposing the Fly IP for your app to Supabase, and locking
       | Supabase down to it. Having Supabase actually within the Fly
       | network is great. Congrats to both teams.
        
       ___________________________________________________________________
       (page generated 2023-12-15 23:00 UTC)