Adopt a durable job queue
Background work was lost on deploys. The team compared a managed queue, database polling, and in-process retries before choosing a durable path.
- Owner
- Kai
- Why
- Reliable retries
Decision and release history for engineering teams
Shiplog helps engineering teams record decisions and track the releases they shape, preserving context, tradeoffs, ownership, and outcomes—so every release informs the next decision.
Keep reasoning with the work
Shiplog preserves what the team knew, what it considered, and who owned the call—then connects that reasoning to the release. New teammates get context without archaeology, and future decisions start with evidence instead of memory.
Background work was lost on deploys. The team compared a managed queue, database polling, and in-process retries before choosing a durable path.
The durable queue shipped alongside a read cache, keeping the release outcome connected to the decisions that shaped it.
Decision-making, unpacked
Get a concise field note on the habits, templates, and tradeoffs behind durable engineering decisions.
New record
Decisions and releases
Includes representative example records to demonstrate Shiplog. They are not customer or internal operational data.
Search updates as you type. Use ↑ and ↓ to move between records, and Home and End to jump. Press Enter to open details.
Loading all decisions…
Portable history
Counting locally stored records…
The JSON file includes only decisions, releases, and their preserved links stored in this browser.
Portable history
Choose a file exported from Shiplog. It is read in this browser only — nothing is uploaded, and nothing is saved until you confirm the summary.
Representative release
This example uses the same release model and linked decision records as the full release history. Expand it to inspect the associated decisions.
Finding the latest release…