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

[SPIKE] Define Event Engine Lookup Process #83

Open
afflom opened this issue Sep 2, 2022 · 3 comments
Open

[SPIKE] Define Event Engine Lookup Process #83

afflom opened this issue Sep 2, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@afflom
Copy link

afflom commented Sep 2, 2022

What is the problem you're trying to solve
The Event Engine lookup process needs to be defined

Describe the solution you'd like
Define the event engine lookup process, so that the client can reliably discover and retrieve Event Engines.

@afflom afflom added the enhancement New feature or request label Sep 2, 2022
@afflom afflom added this to the Runtime groundwork milestone Sep 2, 2022
@jpower432
Copy link
Contributor

jpower432 commented Sep 6, 2022

An initial proposal

sequenceDiagram
    participant Client
    participant Collection
    participant Schema
    participant Event Engine
    Client->>Collection: Where is your schema?
    Schema-->>Client: I'm here!
    Note right of Schema: Must validate<br>Collection!
    Client->>Schema: Where is the event engine?
    Schema-->>Client: "It's here!"
    Client->>Event Engine: "Pulling you now"
    Event Engine-->>Client: "On my way!"
Loading

@jpower432 jpower432 self-assigned this Sep 13, 2022
@jpower432
Copy link
Contributor

@afflom Putting this back into the backlog based on current milestones. We probably need to do some milestone reorg.

@jpower432 jpower432 removed their assignment Oct 17, 2022
@jpower432
Copy link
Contributor

@afflom Should this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants