Event Gateway. - Githubissues

confluentinc / event-streaming-patterns

A collection of Event Streaming Patterns, including problem statements, solutions, and implementation examples.

Apache License 2.0

13 stars 6 forks source link

Event Gateway. #168

Closed krisajenkins closed 3 years ago

krisajenkins commented 3 years ago

Description

Fixes #134.

New Pattern Checklist

[X] Pattern file name should follow docs/pattern-category/pattern-name.md
[X] Create an on-brand diagram (https://docs.google.com/presentation/d/1Zf256Z6fBvre3uclIbmxXsDpnTIxiBX66b13pHbGIYc/edit?usp=sharing)
[ ] Implement ksqlDB or code example (not all patterns will have code, but highly desired)
[X] Provide references
[X] Validate hyperlinks
[X] Spell check (e.g. using aspell)

krisajenkins commented 3 years ago

I'm undecided about giving a code-sample here. The trouble is, doing anything meaningful with the REST API via the command line gets very unwieldy, very quickly. I'll sleep on it, but I'm leaning towards leaving it out. Anyone who know REST will know what shape it's going to have anyway - that's kind of the essence of it being a universal gateway.

benstopford commented 3 years ago

This seems a bit amorphous. Having read the pattern it's not clear to me how to answer to the question: "What is an event gateway?". Intuitively it sounds like an API gateway but that's not what the pattern describes so I don't get a strong sense of what that answer is. I think the question "How does an an Event Streaming Platform provide access to the widest possible range of users?" works but the answer should be a language independent proxy that uses REST, gRPC etc. Adding clients in seems to muddy the water a bit.

krisajenkins commented 3 years ago

Okay folks, I've taken another pass at it and stripped away a lot of the "other languages" stuff. Also updated the diagram. Please take another look.