Design Proposal: Atomic Multi-Component Deployment for DrasiLib#12
Open
danielgerlag wants to merge 1 commit into
Open
Design Proposal: Atomic Multi-Component Deployment for DrasiLib#12danielgerlag wants to merge 1 commit into
danielgerlag wants to merge 1 commit into
Conversation
Introduces a staging model for multi-component deployments that separates slow preparation from fast atomic commitment. This eliminates partial deployment states, compensating rollback complexity, and lock contention during component initialization. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
danielgerlag
requested review from
NValsan,
agentofreality,
amansinghoriginal and
ruokun-niu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Introduces a design proposal for atomic multi-component deployment in DrasiLib using a staging model.
Problem
Deploying multiple components (sources, queries, reactions) as a logical unit is not atomic. Failures mid-deployment leave the system in a partially-deployed state requiring manual recovery.
Proposed Solution
A staging model that separates slow preparation from fast atomic commitment:
GraphTransactionatomically registers all components (sub-millisecond, in-memory only)Key Benefits
Document Location
drasi-lib/Atomic-Deploy/00-atomic-multi-component-deployment.md