Sometimes an application needs Raft semantics, but it does not need another general-purpose distributed system. An existing scheduler, control plane, metadata service, or coordination service may already have its own domain model and API. What it lacks is a safe way for several instances to elect a leader, agree on an ordered command stream, and apply that stream to local state. The usual choices are not always comfortable: implement Raft inside the application; redesign the appl...