Common DB Schema Change Mistakes
- Nikolay Samokhvalov tl;dr: Nikolay covers 18 mistakes, categorized into three big categories of DB schema migration mistakes: "(1) Concurrency-related mistakes. (2) Mistakes related to the correctness of steps. (3) Miscellaneous – mistakes related to the implementation of some specific database feature or the configuration of a particular database."featured in #320
Horrible Edge Cases To Consider When Dealing With Music
- Julien Voisin tl;dr: Julien highlights some of the challenges: "Weird" album names, albums without names, confusing names, long tracks up to 23 hours, tracks with different versions and more. Julien also links to the DB schema to show how to "tame this madness."featured in #305
Yes, I Can Connect To A DB In CSS
- Lee Meichin tl;dr: “As the name might suggest, this is how you connect to a database using CSS. It only works in Chrome, unfortunately, but you can provide any SQLite database you like and query it via CSS.”featured in #289
UK COVID-19 Dashboard Built Using Postgres And Citus For Millions Of Users
- Claire Giordano tl;dr: "In this post you’ll learn about the database challenges the team faced as the dashboard needed to scale—with an eye toward how the UKHSA team uses Azure, the Azure Database for PostgreSQL managed service, and the Citus extension which transforms Postgres into a distributed database."featured in #287
The Best Engineering Interview Question I’ve Ever Gotten, Part 1
- Arthur O’Dwyer tl;dr: "It’s been a while since I was on the receiving end of a software engineering interview. But I still remember my favorite interview question. It was at MemSQL circa 2013... Since MemSQL was a database company, this is a database challenge."featured in #286
42 Things I Learned From Building A Production Database
- Mahesh Balakrishnan tl;dr: Things learned as a tech lead building new infrastructure at a large company: (1) Keep your customers happy; else the rest of this document doesn’t matter. (2) A road-map is a means, not an end. (3) Be conservative on APIs and liberal with implementations. (4) In a transparent codebase with quick review cycles, APIs will leak implementation details unless you gate-keep.featured in #265
How Databases Handle 10 Million Devices In High-cardinality Benchmarks
- Vlad Ilyushchenko tl;dr: "If you're working with large amounts of data, you've likely heard about high-cardinality or ran into issues relating to it. It might sound like an intimidating topic if you're unfamiliar with it, but this article explains what cardinality is and why it crops up often with databases of all types."featured in #234
featured in #207
Things I Wished More Developers Knew About Databases
- Jaana Dogan tl;dr: Useful insights for developers that don't specialize in databases.featured in #180
featured in #169