As lclarkmichalek said, there’s more than one way to skin a cat.

At any rate, I used “equivalent” here to mean that, while different trade-offs have been made, it has the sort of users building the same sort of applications on the same sort of abstractions — it plays the same role, for all intents and purposes.

Scribe doesn't really make decisions about that, it doesn't store checkpoints for readers. Readers are commonly more-than-once.

> Scribe doesn't really make decisions about that

It kind of does, on the write pipeline. Tailers vary, but scribed controls the semantics of how your message gets delivered to LogDevice.