Skip to content
EngineerData
Menu
Design
English

Engineer / Data

Blog

Engineering blog from Engineer ApS, with problems from real projects, their root causes and the fixes that worked.

Most of the notes below started as something that went wrong on a real project. The rest take a known failure apart before it reaches one. We write them down because the fix is usually worth more than the incident, and because the next person to hit it should not have to rediscover it.

  1. Optimise the database before you shard it

    Most databases that seem to need sharding need reading first. The order we work in: measure, tighten, move reads off, partition, then shard.

  2. Selling the last ticket exactly once

    A flash sale oversells on one hot row, not on a big database. What stops it: a conditional write, holds that expire, and a saga.

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark