Commit dacbcf24 authored by Corey O'Connor's avatar Corey O'Connor


parent f0275363
......@@ -232,7 +232,7 @@ $ curl localhost:10000/_ops/groups
Note the `operators` attribute. Using the premium license server this would contain the users
authorized to access that group. The free license server ignores this attribute.
authorized to be operators in that group. The free license server ignores this attribute.
#### Groups Extend the API
......@@ -452,6 +452,24 @@ The standalone version persists to the directory provided to the `--state` comma
When deployed to kubernetes the service can also persist to a database such as Amazon's DynamoDB
or Cassandra.
#### Operator Access
The REST endpoints above are an interface to the service's event protocol. The
service designer defines the REST endpoint as a request event and expected
response event. How this request event is handled is defined separately.
One purpose of this separation between endpoints and service protocol is to
differentiate "users" of a service from "operators" of that service. Operators
have additional access to services. Including access to the service protocol
directly. This enables operators, for example, to post requests that are
not part of the exposed endpoints.
This additional access is exposed under the "_ops" endpoints of a service
and group. We've already used a few of the operator endpoints above. Direct
access to the protocol is provided via the:
- `_ops/requests` - POST envelope containing protcol message
#### Capturing Events
If we have a model of our business events we can build and instantiate service fragments that
......@@ -468,6 +486,8 @@ TODO:
3. service events
2. demo capturing a service modeled event
aka schema on write
#### Requests
A request is a unique interaction with a client. Requests are implicitly
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment