BrighterCommand/Brighter

[Feature] Add support to Oracle

Open

#3,658 opened on Jul 10, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)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

Oracle has interesting product that Brighter could integrate to improve support for enterprise user

  • Oracle Database for inbox, outbox and distributed lock
  • Oracle NoSQL Database for inbox, outbox and distributed lock
  • Oracle Berkeley DB for inbox, outbox and distributed lock
  • Oracle Advance Queue as a messaging gateway (using Oracle Database as messaging gateway)
  • Oracle Transactional Event Queues as a messaging gateway (using Oracle Database as messaging gateway)
  • Oracle Queue Service as a messaging gateway
  • Oracle Cloud Infrastructure (OCI) Object Storage as luggage store

Contributor guide

Research direction
Investigate Oracle Database, Oracle NoSQL Database, Oracle Berkeley DB, Oracle Advanced Queue, Oracle Transactional Event Queues, Oracle Queue Service, and OCI Object Storage to understand their APIs and how they can be integrated with Brighter's existing abstractions for inbox, outbox, gateway, and luggage store. Review Brighter's architecture and extension points. Design a high level integration plan for each component.
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.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
C#.NETOracle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30