...
It will consist of the complete JSON representing what CBS/Consul keeps for microservice (and not only the changes).
Note
...
We have started an implementation for listening to changes in a subtree of JsonObject based on Merkle Tree data structure. But we are still unsure if we will continue this or not. Please let me know if you find it useful. For now we are recommending to first convert the JsonObject to domain classes and then subscribe to changes in these objects if you want to have a fine-grained control over update handling. It's an experimental API so it can change or be removed in future releases.
An issue arises when the Flux stream terminates with an error. In that case, since error is a terminal event, stream that updates from Consul is finished. In order to restart periodic CBS fetches, it must be re-subscribed. What is the suggestion about it?
...