starter doc explaining key concepts from the spec#53
Conversation
Signed-off-by: Sarah Allen <sarahallen@google.com>
Signed-off-by: Sarah Allen <sarahallen@google.com>
Signed-off-by: Sarah Allen <sarahallen@google.com>
Signed-off-by: Sarah Allen <sarahallen@google.com>
|
This is a great start @ultrasaurus. We should link to this in the main README, so newcomers who read the brief description in the README have a clear path to learn more. |
|
@ultrasaurus @clemensv Having our recent user story discussion in mind, I wonder if we could derive some architectural patterns of systems dealing with events. I don't mean complete systems. I observed that during discussions there are some reoccuring examples like the API gateway and the web hook, or mapping events to a topic structure on a broker. Maybe there are also patterns specific to interoperability like event gateway that do more than simple forwarding. If the term "pattern" causes some people to roll their eyes, we could also just call them examples. I just think that in our discussions it might help to simply refer to examples/patterns from the list. |
|
if #283 is adopted then I think moving this info into the primer.md would be good |
For reviewers (and later implementers) to understand the specification, we need to provide
some context for the kinds of systems that use events and the problems we're solving.
See #37
This PR defines a few terms with an overly simplified diagram. Once we agree on these terms,
then it will be easier to add the other components that will need to be present in a typical system.