News for hackers. Stuff that matters.

A comment on Tarsnap outage (July 2-3, 2023) postmortem. Parent comment

Re:Tarsnap outage (July 2-3, 2023) postmortem by zetalyrae on Thursday July 27, 2023 @07:32AM (#36891973)
How is not rolling your own database a good thing? Mainly because the business of tarsnap is 1) encrypted 2) backups, not building a database storage engine.
[ Parent | on HN ]
Re:Tarsnap outage (July 2-3, 2023) postmortem by catiopatio on Thursday July 27, 2023 @12:03PM (#36895634)
It’s cute that you think implementing client-side encrypted, deduplicated backups doesn’t involve building a database storage engine.
[ Parent | on HN ]
Re:Tarsnap outage (July 2-3, 2023) postmortem by catiopatio on Thursday July 27, 2023 @03:29PM (#36898875)
Implementing client-side encrypted, deduplicated, snapshot-enabled backups inherently requires building a minimal storage engine to represent your opaque log-structured data.

Embedding the log-structured representation of user data in Postgres would increase complexity and overhead without offering significant resiliency or recoverability advantages — in fact, quite the opposite.

[ Parent | on HN ]