This is a MVP for Serverless Postgres.
1/ It uses Fly.io[0], which can automatically pause your database after all connections are released (and start it again when new connections join).
2/ It uses Oriole[1], a Postgres extension with experimental support for S3 / Decoupled Storage[2].
3/ It uses Tigris[3], Globally Distributed S3-Compatible Object Storage. Oriole will automatically backup the data to Tigris using background workers.
I wouldn't recommend using this in production, but I think it's in a good spot to provoke some discussion and ideas. You can get it running on your own machine with the steps provided - connecting to a remote Tigris bucket (can also be an AWS S3 bucket).
[0] https://fly.io
[1] https://www.orioledb.com/
[2] Oriole Experiemental s3: https://www.orioledb.com/docs/usage/decoupled-storage
[3] Tigris: https://www.tigrisdata.com/
It seems like it still needs memory/cpu resources locally (sized properly) to handle the returned data.
It also seems like an incredibly bad idea to use with any remote data store that charges for network traffic. ie Amazon AWS
You could easily give yourself a many thousand dollar bill for a month if you start using that backend data store in a serious way. :( :( :(
---
That being said, it's a nifty idea conceptually. Just be aware of likely operational costs if you try using it. (!)