Novices: keep in mind that this is actually just the minimum viable code to support a distributed system. The next thing you need is enough tooling and features

Novices: keep in mind that this is actually just the minimum viable code to support a distributed system. The next thing you need is enough tooling and features to support integrity and reliability guarantees. For example, when network instability forces each of your operations to fail in an unexpected way, you need to be able to resolve the different failure modes and reestablish a consistent application and network state. The Raft algorithm doesn't do that for you. It's like how TCP doesn't guarantee that your data will be written or processed or transmitted without corruption; only that it will be received without corruption. You will still get corruption after recv() and before send(), and you have to handle those cases, or your application will begin to introduce unknown data corruption. And when that happens you need the tooling and telemetry to address it after the fact, "distributedly".