knative / knative/specs

[Trigger - Spec] Ordered events support

Open
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
38
Forks
48
PR merge metrics
No merged PRs in 30d

Description

This issue is to discuss whether First In First Out (FIFO) or ordered events should be something that's configurable through the spec.
The prominent implementations of Broker/Trigger currently already support ordered events through annotations:

Kafka: By setting kafka.eventing.knative.dev/delivery.order to ordered or unordered
Rabbitmq: FIFO vs high throughput is controlled by the same annotation rabbitmq.eventing.knative.dev/parallelism. When == 1, events will be in order.

Ordered events can be an important part of an application's setup and using annotations to configure it requires users to dig through the implementers documentation.

Open questions:

  • Should supporting ordered events be a requirement for implementations or be left as a MAY support?
  • Where in the spec should the ordered field be placed? One suggestion during the working group meeting was in the DeliverySpec
  • Should the default be ordered events?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Trigger spec, especially the proposed DeliverySpec location, and compare the existing Kafka and RabbitMQ annotation behavior described in the issue. Done means resolving whether ordered events are required or optional, deciding where the ordered field belongs, and defining the default; no specific file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
kafka, rabbitmq
Domain
backend-api-design, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.