golang hybrid store compatible with omniql
- use nats for communication (initially); after it should laverage hybrids for this
- use consul for store the resources (wrap consul in kv interface), this will allow use another kvs in the future
- for the first version, please don't add the versioning functionality of omniql
- hear queries on the nats channel
query.*, where * is the resource id - return query result on the channel
component.componentId, where componentID is the resource making the query - hear command on the nats channel
command.*where * is the resource id - return command result on the channel
component.componentId, where componentID is the resource making the query - store the resources in the kv storage in the binary format
- this implementation only accepts stacks of type state. see 3