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

Sample App: BookReview Service: Broker implementation #5918

Closed
Leo6Leo opened this issue Mar 19, 2024 · 0 comments · Fixed by #5928
Closed

Sample App: BookReview Service: Broker implementation #5918

Leo6Leo opened this issue Mar 19, 2024 · 0 comments · Fixed by #5928
Assignees

Comments

@Leo6Leo
Copy link
Member

Leo6Leo commented Mar 19, 2024

!!!The description for this issue is work in progress.

Problem

In this issue, we are implementing the knative broker that provide all the request routing that make the book review feature works. It connects the BookReview Service. When the broker receive a cloudevent from the BookReview Service, the broker should be able to correctly route the event to the correct sink by filtering the cloudevents. ML services, and notification services.

More details can be found on the design doc.

Persona:

Which persona is this feature for?
Administrators and developers

Exit Criteria

  • Yaml files that will deploy Knative Eventing Broker that can achieve all the routing as described above.
  • A detailed documentation that explains it and include the setup guide.

Time Estimate (optional):
How many developer-days do you think this may take to resolve?
2-3

Additional context (optional)

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant