2,259 karma · joined May 2, 2016
If I remember correctly, it was a us-east-1 issue specifically. Why is everyone hosted in us-east-1, especially in Europe where stable and reliable regions are available (eu-west-1, eu-west-3, ...)?
The article seems a bit misleading. AFAIK, MariaDB (InnoDB) have to "vacuum" too. The implementation details are different between InnoDB and PostgreSQL, and maybe the InnoDB's Undo Log approach is less subject to bloat and maintenance cost, but it still exist as the InnoDB Purge Thread: https://mariadb.com/docs/server/server-usage/storage-engines...
I guess it depends on the audience. Our audience is tech-savvy and like RSS feeds, and it can change everything.
You need to make one big "spike", then some people will subscribe to your RSS feed, and some of them will silently follow you and read the future articles that won’t make it to the HN front page.
But I still agree with the point.
I shared this article a few weeks ago, discussing the problems with this kind of approach: https://notnotp.com/notes/do-not-encrypt-ids/
I believe it can make sense in some situations, but do you really want to implement such crypto-related complexity?
I’ve always been puzzled about the fact there was no checksum by default. Integrity of data is a core job of a DB after all. I’m curious to know if there was a technical justification for that.
I believe the book focuses on client-side TS apps?
If I were hosting something subject to potential egress overconsumption, it’d be interested I guess