gc pinning (i.e. the software is released, don’t purge it without pulling the pin). and potentially look at options to drop the database entirely. I mean at that point it’s probably a rewrite, but i’d love to a design that stores bulk metadata updates as a WAL in the blob store (with eventual compaction into an index), s.t. that you can have a stateless cache server and a blob store and you are golden. I know s3 can do this safely with conditional writes, I just don’t know if other not s3 but s3-compatible blob stores can do that kind of thing? Anyway, a good gc pinning story would be incredible, and if there were a pot I would try to throw money into it for that feature.
EDIT: I mean maybe you could do it without conditional writes, but I think the story gets much more complicated. I’d also be prepared to run 3 servers instead of one with RDS (i.e. way cheaper to run 3 t4g micros than one HA RDS, and just replicate txn metadata into raft log written back to s3), but now I’ve strayed into @bme’s fantasy cache server.