|
|
|
|
|
by jgraettinger1
1985 days ago
|
|
Neat. This is very similar to [0], which is _not_ a cache but rather a complete mirror of an Etcd keyspace. It does Key/Value decoding up front, into a user-defined & validated runtime type, and promises to never mutate an existing instance (instead decoding into a new instance upon revision change). The typical workflow is do do all of your "reads" out of the keyspace, attempt to apply Etcd transactions, and (if needed) block until your keyspace has caught up such that you read your write -- or someone else's conflicting write. [0] https://pkg.go.dev/go.gazette.dev/core/keyspace |
|
I guess Go package discovery remains an unsolved problem.