Pod Types & Composability¶
Lane7 Blueprints offer composability at two independent levels. Understanding both helps you get the most out of the catalog blueprints and know when to request a custom network.
Blueprint composability — five pod types combine into networks of any topology, protocol, environment, and security mode. The catalog is a curated starting point. The same building blocks can compose any architecture you need.
App logic composability — every pod's app.py has a Section 1 for business logic and a Section 2 for WoSP networking. Section 1 is yours to replace freely. Section 2 stays fixed.
| Composability Type | What changes | What stays fixed |
|---|---|---|
| Blueprint | Topology, protocol, security mode, environment | WoSP security guarantees |
| App Logic | Business logic (Section 1) | WoSP networking (Section 2) |
These two types are independent. You can deploy a catalog blueprint as-is (no Section 1 work needed) and it runs with full WoSP security. You can also customize Section 1 extensively without changing the topology.
In this section¶
- Two Kinds of Composability — the conceptual foundation
- The Five Pod Types — building blocks, roles, and ingress/egress patterns
- Building Networks from Pod Types — how pod types combine into topology patterns with Mermaid diagrams
- The Four Dimensions — security mode, environment, protocol, and scale as design choices
- Mixed-Protocol Blueprints — combining HTTP, WebSocket, and gRPC pods in a single network