Skip to content

docs: clarify when to use bindings instead of state management - #5469

Open
VictorMoni wants to merge 2 commits into
dapr:v1.19from
VictorMoni:docs/clarify-bindings-state-management-3691
Open

VictorMoni wants to merge 2 commits into
dapr:v1.19from
VictorMoni:docs/clarify-bindings-state-management-3691

Conversation

@VictorMoni

Copy link
Copy Markdown

Explain binding-specific capabilities, compare bindings with the state API, and illustrate the choice using Azure Blob Storage. Qualify portability claims so that changing binding types is not presented as unconditional.

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have tabpane

In addition, please fill out the following to help reviewers understand this pull request:

Description

Issue reference

Explain binding-specific capabilities, compare bindings with the state API,
and illustrate the choice using Azure Blob Storage. Qualify portability
claims so that changing binding types is not presented as unconditional.

Signed-off-by: Victor Moni <victor-moni@hotmail.com>
@VictorMoni
VictorMoni requested review from a team as code owners November 3, 2026 17:40
@CasperGN CasperGN self-assigned this Nov 3, 2026
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.

2 participants