BrighterCommand/Brighter

[Feature] Support a CosmosDb Outbox

Open

#1777 opened on Oct 19, 2021

View on GitHub
 (18 comments) (2 reactions) (1 assignee)HTML (1,898 stars) (295 forks)batch import
.NET0 - BacklogV10.Xfeature requesthelp wanted

Description

Problem We don't support the Outbox pattern for CosmosDb. increasingly, Azure customers may be using CosmosDb for entities and we should support working with the Outbox and CosmosDb

Describe the solution you'd like

  • Support for using it with a CosmosDb TransactionalBatch

Describe alternatives you've considered

  • Consider support for using the CosmosDb Change Feed instead of a TransactionalBatch as the source of writes to the Outbox. This would be a separate process and whilst valuable represents the story after this one
  • It's possible that a 'single table' approach works with CosmosDb as well.

Contributor guide

Tech stack
csharp
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C# knowledgeBrighter framework basicsCosmosDb concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine existing outbox implementations in Brighter (e.g., for SQL Server) to understand the pattern. Review the CosmosDb SDK documentation and TransactionalBatch API. Check issue comments for any design discussions and requirements. The implementation should likely be in a new provider project under Brighter's source.