Ordering per key, concurrency across keys
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp, postgresql
- Domain
- databases, distributed-systems
Research direction
Start by reading the repository’s outbox implementation and its tests to find where messages are selected and dispatched. Implement ordering within each key while allowing separate keys to be processed concurrently; add tests that verify both ordering and parallelism. Done when those tests pass for the supported SQL Server and PostgreSQL backends.
Written by the indexing model from the issue text.
Description
Messages with the same ordering key go out in the order they were saved; different keys can be sent in parallel.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- Avg merge
- 3m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from softvasco/outbox-kit
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
softvasco/outbox-kit#9 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 38/100
softvasco/outbox-kit#24 ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 48/100
softvasco/outbox-kit#23 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
softvasco/outbox-kit#22 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 47/100
softvasco/outbox-kit#21 ·
All issues in softvasco/outbox-kit
Similar issues
-
Incorrect loop bound in SizeOptIListSelectIterator.ToListPossibly taken @equmagg claimed this today. Openarea-System.Collections untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
dotnet/runtime#137126 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#64658 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70370 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NethermindEth/nethermind#15684 ·
Maintainers usually reply within 1 day
-
area/ai-assistant squad/flyt
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Altinn/altinn-studio#21798 ·
Maintainers usually reply within 1 day