Yeah, I'm surprised this pattern doesn't have a more general name.
replyI've also used it to synchronize content for local multi-window editing applications: each window is its own process but routes through one "coordination" process to ensure consistent ordering.
Easily solves some cross-process concurrency issues.
It does have a name:
replyIt's not quite the same since we aren't doing any sort of interpolation. I would acknowledge it's a similar idea though. Perhaps the similarity is one reason we came to this solution as a game studio.
replyIn this case it's just a (transaction/commit) log. Very common in distributed systems, databases, and filesystems.
replyI misread the question but it could be a read-your-writes consistency of the transaction log!
reply