cloud-security-posture-management
A canister is a smart contract on the Internet Computer (ICP) blockchain that consists of both WebAssembly bytecode and memory state.
Canister Lifecycle: 1. Creation and cycle funding. 2. Installation of Wasm code. 3. Inter-canister calls. 4. Upgrades (handling state migrations). Technical Stack: Motoko, Rust, WebAssembly. Economic Model: Reverse gas (Cycles), Governance via NNS.
graph LR
Center["cloud-security-posture-management"]:::main
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Think of a regular [smart contract](/en/terms/smart-contract) like a calculator that only remembers the last number you typed. A canister is like a whole mini-computer that lives on the [blockchain](/en/terms/blockchain). It has its own code, its own memory (like a hard drive), and it's 'pre-paid' by the developer so you can use it for free, just like you use regular websites.
🤓 Expert Deep Dive
Canisters represent 'Orthogonal Persistence', meaning the developer doesn't need to manually save data to a database; the memory state is automatically persisted by the IC's consensus layer. They are compiled to WebAssembly (Wasm), allowing for near-native execution speed. Canisters communicate via an asynchronous messaging model (Request-Response) across different 'subnets', which provides horizontal scaling. Security is enforced by the 'Chain Key Cryptography', which allows the IC to verify the state of any canister with a single public key, enabling web-speed interactions and direct HTTP requests to the outside world safely.