It's really nothing special, just some general principles that are sensible to me:
- Production levelling/burst smoothing early in the process, so other steps don't have to bother with variability.
- WIP constraints/limited queue sizes both to reveal problems and improve latency.
- Kanban/backpressure to stop the problems at the source, and help troubleshooting.
- Using Little's law as a guideline in tradeoffs between batch size and latency and size of system.
- Deliberately shed load when it cannot be served in time, rather than vainly holding on to it for dear life because "surely we cannot outright reject work?!"
- Dropping at the head of queues to improve latency and serve the fresher requests sooner.
There's probably a lot more, and TFA covers some of it too.
