[micvbang]

Thanks, great question!

My strategy was to start out by implementing the underlying storage primitives first, and then look into which transport to implement later. The transport of course can have a large impact on the required storage primitives, but in my case I built it the other way around since I knew what primitives I would need in my applications.

I've been playing with the thought of implementing (parts of) the Kafka API, but I honestly haven't considered the transport that much yet :)

[kittiepryde]

Reading, 'ensuring that data is actually written and stays written is rather difficult', immediately reminded me of https://github.com/microsoft/FASTER (its not written in Go though), which is basically dealing with just that outlet ( except I think the KV store might be ram heavy, been a bit since I last looked at it )

[micvbang]

Hadn't heard of this - it looks very interesting. Thanks for the reference!