The “consensus” in raft is simply a way to guarantee durability of writes (among other things) in distributed setup. In your case the producer node gets a guara

The “consensus” in raft is simply a way to guarantee durability of writes (among other things) in distributed setup. In your case the producer node gets a guarantee that it did in fact commit its route to the db. Ofc you can achieve similar outcome with something like gossip + repeated announcements. It would probably depend on specifics which approach is more efficient