Blockchain infrastructure and DevOps
What separates a chain that works from a chain that holds.
A transversal track: the protocol tracks draw their operations workshops from it instead of duplicating them. A Cosmos participant and an Avalanche participant attend the same monitoring workshop.
It runs from infrastructure as code through to the disaster recovery drill, by way of the public RPC service BAC operates for its own testnet.
The track that makes a chain operable by someone other than its author.
- workshops
- 15
- taught hours
- 55
- Track lead
- DevOps / Blockchain Infrastructure Engineer
Modules
Infrastructure as code
Provisioning, idempotent configuration, continuous integration.
Deployment and orchestration
Cloud topology, a production node, and the limits of orchestration.
Observability and incidents
Metrics, logs, on-call, backups and disaster recovery.
Public service and secrets
RPC infrastructure, capacity, secrets management, then full delivery.
Capstone
A complete operated infrastructure
Deliver a network's infrastructure — validators, RPC, monitoring, backups, recovery — fully rebuildable from the repository.
- 01Full rebuild by the panel from the repository
- 02Timed disaster drill, passed within the committed window
- 03Published operations and on-call runbooks
The other tracks
FOUND
Foundation
20 workshops
DOT
Polkadot
12 workshops
SUB
Substrate / Polkadot SDK
18 workshops
COSMOS
Cosmos SDK
25 workshops
AVAX
Avalanche
20 workshops
TIA
Celestia and modular blockchains
20 workshops
XCHAIN
Interoperable systems engineering
15 workshops
SEC
Blockchain security
15 workshops
ARCH
Blockchain architecture
10 workshops