Skip to content

State persistence architecture documentation#11284

Open
brooke-hamilton wants to merge 7 commits intoradius-project:mainfrom
brooke-hamilton:brooke-hamilton/state-architecture-doc
Open

State persistence architecture documentation#11284
brooke-hamilton wants to merge 7 commits intoradius-project:mainfrom
brooke-hamilton:brooke-hamilton/state-architecture-doc

Conversation

@brooke-hamilton
Copy link
Member

@brooke-hamilton brooke-hamilton commented Feb 20, 2026

Description

Adds a new architecture document describing the state persistence subsystems in Radius (database, secret store, message queue).

Changes

  • docs/architecture/state-persistence.md — New document covering the three pluggable state persistence subsystems: database.Client, secret.Client, and queue.Client. Includes Mermaid diagrams, interface descriptions, implementation details, and data flow explanations.

Type of change

  • This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and does not change the functionality of Radius (issue link optional).

Contributor checklist

Please verify that the PR meets the following requirements, where applicable:

  • An overview of proposed schema changes is included in a linked GitHub issue.
    • Yes
    • Not applicable
  • A design document PR is created in the design-notes repository, if new APIs are being introduced.
    • Yes
    • Not applicable
  • The design document has been reviewed and approved by Radius maintainers/approvers.
    • Yes
    • Not applicable
  • A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
    • Yes
    • Not applicable
  • A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
    • Yes
    • Not applicable
  • A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
    • Yes
    • Not applicable

Copilot AI review requested due to automatic review settings February 20, 2026 21:53
@brooke-hamilton brooke-hamilton requested review from a team as code owners February 20, 2026 21:53

This comment was marked as outdated.

Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
@brooke-hamilton brooke-hamilton force-pushed the brooke-hamilton/state-architecture-doc branch from eee6054 to 0d83d05 Compare February 20, 2026 22:00
@brooke-hamilton brooke-hamilton changed the title State persistence architecture documentation and Copilot skill for architecture diagramming State persistence architecture documentation Feb 20, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

@codecov
Copy link

codecov bot commented Feb 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.15%. Comparing base (5ae6100) to head (cfc6691).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11284      +/-   ##
==========================================
- Coverage   51.16%   51.15%   -0.02%     
==========================================
  Files         682      682              
  Lines       43433    43433              
==========================================
- Hits        22223    22217       -6     
- Misses      19066    19069       +3     
- Partials     2144     2147       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Clarify terminology and configuration in the state persistence
architecture document. Add a Terminology section defining
'client' as a data-access abstraction, correct the YAML config
key from 'database' to 'databaseProvider', and expand Step 7
with real configuration examples for APIServer (Helm) and
PostgreSQL (local development) deployments.

Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
@nithyatsu nithyatsu self-requested a review March 2, 2026 20:00
Copy link
Contributor

@nithyatsu nithyatsu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks nice to me.

  • I am assuming we leave DE out since it doesnt directly interact with database.
  • Its probably just me, but it might be helpful to point out that all microservices today share these components ( ucp + two rps write/read from/to same db instance)
  • the edges seem to go behind the nodes in first layer. But I am not sure we can control that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants