Talk about your next project
Redpanda executive brief

The lesson

Win a technical argument against a rival's default by giving the reader both a proof and a reproduction they can run themselves.

The move

The page opens by listing Redpanda's design choices, ending with always using fsync before acknowledging writes with acks=all, and says the post will show 'both in theory and in practice' that losing unsynced data on one node causes global data loss. Question-style headings then build the case: 'What is fsync?', 'What is replication for?', and 'Can replication reduce the safety risks of running a system without fsync?' That last section names the opposing view as 'a common misunderstanding.' 'Proof of impossibility' argues by contradiction with a three-node example, 'Counter example' walks through terminal commands that reproduce the data loss on a local Kafka setup, and a short 'Conclusion' closes the post.

Why it works

  • Our readStating the opposing belief fairly before rejecting it lets a skeptical engineer see that their own view was considered.
  • Our readPairing a formal proof with commands a reader can run gives two separate routes to belief, one for theorists and one for practitioners.
  • Our readThe question headings in the table of contents read as the steps of the argument, so a reader can jump to the part they doubt.

What not to copy

Don't copy the fsync topic or the Kafka comparison, which depend on Redpanda's own architecture. Keep the sequence of definitions, the stated misconception, a proof, and a reproducible counter example.

More from Redpanda

More executive briefs

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.