BrighterCommand/Brighter

[Feature] Support a CosmosDb Outbox

Open

#1,777 opened on Oct 19, 2021

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

Repository metrics

Stars
 (1,898 stars)
PR merge metrics
 (Avg merge 8d 18h) (29 merged PRs in 30d)

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

Research direction
Examine the existing outbox implementation in Brighter for relational databases, then study how CosmosDb TransactionalBatch can be used to achieve atomic writes for the Outbox pattern. Also consider the alternative of using CosmosDb Change Feed as a source of outbox writes, understand its trade offs, and determine how to integrate it with Brighter's existing architecture.
Tech stack
csharpazure
Domain
backenddatabasecloud
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.
3-5 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#Azure CosmosDBBrighter framework basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30