It's one thing to install a single Postgres server, configure wal-e or pgBackRest, and watch and babysit your single production database. It's another to install Postgres and say your job is done as long as the server is up, it's the user's problem.
How do you give a great database experience to thousands of users without dying from pager burnout? Crunchy Bridge is an attempt for a better option for Postgres hosting. We'll look mostly at how it's built with a little time on why we feel the need for there to be yet another Postgres managed service offering.
Louise is a SQL/python/ruby developer. She is a senior software engineer at Crunchy Data where she works on Crunchy Bridge, a multi-cloud managed postgres service. Before that she was working as a developer focusing on database performance as Citus Data and Ulule (a crowdfunding platform).
Craig currently runs Crunchy Bridge, a multi-cloud fully managed Postgres service from Crunchy Data. Previously he ran product for Heroku Postgres, ran product at Citus Data, and product for Azure Postgres. He curates Postgres weekly, a weekly newsletter of interesting Postgres content.