Managing critical state and consensus
Keeping critical configuration and metadata consistent and highly available using distributed consensus algorithms and careful design.
Managing critical state and consensus
Keeping critical configuration and metadata consistent and highly available using distributed consensus algorithms and careful design.
Critical vs non-critical state
Critical state includes data whose corruption or loss would be very costly: configuration, membership, account balances, etc.
Such state often lives in strongly consistent stores or is managed by well-understood distributed systems primitives.
Ready to see how this works in the cloud?
Switch to Career Paths for structured paths (e.g. Developer, DevOps) and provider-specific lessons.
View role-based pathsSign in to track your progress and mark lessons complete.
Discussion
Questions? Discuss in the community or start a thread below.
Join DiscordIn-app Q&A
Sign in to start or join a thread.