Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

starter doc explaining key concepts from the spec #53

Closed
wants to merge 4 commits into from

Conversation

ultrasaurus
Copy link
Contributor

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.

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>
@austencollins
Copy link
Contributor

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.

@deissnerk
Copy link
Contributor

@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.

@duglin
Copy link
Collaborator

duglin commented Jun 20, 2018

if #283 is adopted then I think moving this info into the primer.md would be good

@duglin duglin mentioned this pull request Jun 29, 2018
@duglin duglin closed this in #238 Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants