On: Bolt: A low-level key/value database for Go

[fishnchips]

Stateless nodes is just one possible type of architecture - nothing in the language itself forces you to adopt it.

[cbroglie → fishnchips]

Of course. But I'm asking b/c I can't think of a situation where I would want to have stateful web nodes.

[tracker1 → cbroglie]

Management interface for monitoring, irc/chat host, pretty much anything interactive to a persistent backend.

Go can be used for far more than just web nodes.. it can be used for any number of network or stand-alone applications.

[fishnchips → cbroglie]

My use case would be small local tools that need to keep some state. Essentially anywhere a SQLite would be useful. I don't think this was designed to serve as a database to back anything more 'serious'.

[gravitronic → fishnchips]

We use it to store and serve 100s of GB of data with a custom query interface on top.

[fishnchips → gravitronic]

What's the replication strategy then?

[benbjohnson → fishnchips]

It's not the data authority. It feeds in data from Kafka and structures it in an optimized way for querying. If a node dies then it can copy from another node and restart from an offset in Kafka. Kafka essentially works as a distributed write-ahead log (WAL).

[ma2rten → benbjohnson]

Why and for what do you use that architecture?