> it is only practical for situations where the write rate (<100/s total) and data volumes (<10GB total) are low.<p>This comment from the GitHub project page is pretty important. Configuration data often sees slow change, and isn't huge so a custom approach seems viable. I wonder how close they are to that 100/s ceiling.<p>There's also an unmentioned transition to eventual consistency happening here:<p>> The implications of this decoupling is that the data at each instance is usually slightly out-of-date (by 1-2 seconds).<p>> The reader API provides a way to fetch an approximate staleness measurement that is accurate to within ~5 seconds.<p>That's could lead to more complex application logic or risk of confusing users with stale behavior. No free lunch here.<p>[1] <a href="https://segment.com/blog/separating-our-data-and-control-planes-with-ctlstore/" rel="nofollow noreferrer">https://segment.com/blog/separating-our-data-and-control-pla...</a><p>[2] <a href="https://github.com/segmentio/ctlstore">https://github.com/segmentio/ctlstore</a>