Tag: databases

  • Load Testing Without the Hype

    Load Testing Without the Hype

    Latency percentiles tell a story that averages politely hide. A boring deploy pipeline is a feature, not a lack of ambition. The rollback plan should exist before the rollout plan is approved. A small example Latency percentiles tell a story that averages politely hide. We measured first, and the bottleneck was not where anyone expected.…

  • What I Learned About Monorepos the Hard Way

    What I Learned About Monorepos the Hard Way

    Naming things well saved us more time than any framework migration. Caches are easy to add and surprisingly hard to remove. Latency percentiles tell a story that averages politely hide. Going further Small pull requests get real reviews, large ones get approvals. Tests are documentation that fails loudly when it goes stale. If the error…

  • Why Error Budgets Matter More Than You Think

    Why Error Budgets Matter More Than You Think

    A boring deploy pipeline is a feature, not a lack of ambition. Our on-call rotation improved the day we deleted half of the alerts. If the error message does not say what to do next, it is half an error message. A small example Logs answer questions you knew to ask; traces answer the ones…

  • Ten Notes on Dependency Updates

    Ten Notes on Dependency Updates

    The fastest query is the one you never send, but the second fastest has a good index. The rollback plan should exist before the rollout plan is approved. Every retry needs a budget, otherwise it is just a slower outage. A small example Feature flags are debt with an expiration date you must actually enforce.…

  • Error Budgets: Mistakes I Keep Seeing

    Error Budgets: Mistakes I Keep Seeing

    The rollback plan should exist before the rollout plan is approved. The fastest query is the one you never send, but the second fastest has a good index. A boring deploy pipeline is a feature, not a lack of ambition. A small example Latency percentiles tell a story that averages politely hide. Security is mostly…

  • Debugging Monorepos at 3 a.m.

    Debugging Monorepos at 3 a.m.

    We measured first, and the bottleneck was not where anyone expected. Our on-call rotation improved the day we deleted half of the alerts. The rollback plan should exist before the rollout plan is approved. What didn’t Every retry needs a budget, otherwise it is just a slower outage. We wrote the migration twice: once to…

  • Why Dependency Updates Matter More Than You Think

    Why Dependency Updates Matter More Than You Think

    Naming things well saved us more time than any framework migration. Every retry needs a budget, otherwise it is just a slower outage. Logs answer questions you knew to ask; traces answer the ones you did not. A small example We wrote the migration twice: once to learn, once to ship. Logs answer questions you…

  • What I Learned About Database Indexes the Hard Way

    What I Learned About Database Indexes the Hard Way

    Every retry needs a budget, otherwise it is just a slower outage. Small pull requests get real reviews, large ones get approvals. Naming things well saved us more time than any framework migration. Context Feature flags are debt with an expiration date you must actually enforce. Caches are easy to add and surprisingly hard to…

  • Why Refactoring Matter More Than You Think

    Why Refactoring Matter More Than You Think

    Caches are easy to add and surprisingly hard to remove. The fastest query is the one you never send, but the second fastest has a good index. The best architecture diagram is the one the new hire can redraw from memory. What didn’t Small pull requests get real reviews, large ones get approvals. Our on-call…

  • What I Learned About Error Budgets the Hard Way

    What I Learned About Error Budgets the Hard Way

    Latency percentiles tell a story that averages politely hide. Security is mostly about saying no to defaults that were convenient in 2010. Naming things well saved us more time than any framework migration. Details Caches are easy to add and surprisingly hard to remove. The fastest query is the one you never send, but the…

  • Debugging Rate Limiting at 3 a.m.

    Debugging Rate Limiting at 3 a.m.

    Every retry needs a budget, otherwise it is just a slower outage. The rollback plan should exist before the rollout plan is approved. Feature flags are debt with an expiration date you must actually enforce. Trade-offs The best architecture diagram is the one the new hire can redraw from memory. Feature flags are debt with…

  • Ten Notes on Database Indexes

    Ten Notes on Database Indexes

    Security is mostly about saying no to defaults that were convenient in 2010. A boring deploy pipeline is a feature, not a lack of ambition. We measured first, and the bottleneck was not where anyone expected. Context Small pull requests get real reviews, large ones get approvals. Naming things well saved us more time than…