Currently we save a Command key, and then 0 (in case of an error) or more Events (in case there was a change).
We can simplify this by saving a single ChangeSet structure that includes all this. Just like WalStore does.
This will simplify the logic around finding these files. Each change will be in a single atomic stored key. It will also reduce the number of keys (files for most deployments).
Currently we save a Command key, and then 0 (in case of an error) or more Events (in case there was a change).
We can simplify this by saving a single ChangeSet structure that includes all this. Just like WalStore does.
This will simplify the logic around finding these files. Each change will be in a single atomic stored key. It will also reduce the number of keys (files for most deployments).