iii-architecture-patterns
Composing iii primitives into backend architectures: durable workflows
by iii-hqFree
Description
iii-architecture-patterns is a skill that helps an agent compose iii primitives into larger backend architectures. Use it when a task is bigger than one function or trigger. The skill starts from the requirement and picks a pattern, then implements it with Function, Trigger, Worker, state, queues, streams and pub/sub. The patterns it maps are a durable workflow for sequential work with retries, a dead-letter queue and step tracking, where functions are chained through named queues and progress is kept in state. A reactive backend keeps views, metrics, caches or clients in sync, using state triggers plus stream or pub/sub side effects. An agentic backend runs specialized AI agents that hand work to each other, with one function per agent, queue handoffs and shared state. Event-driven CQRS separates commands from projections, so commands publish events and projections update independently from an event log kept in state. An effect pipeline composes small functions synchronously with trigger(), which keeps the composition pure and traceable. A low-code automation pattern chains trigger, transform and action nodes with enqueue, for webhook and cron chains. The skill is installed with npx skills from the iii-hq/iii repository.…
Highlights
- Durable workflows with retries and step tracking
- Reactive backends keyed to state triggers
- Agentic backends with queue handoffs
- Event-driven CQRS with projections
- Effect pipelines and low-code automation chains
Ratings & Reviews
No ratings yet
Be the first to rate iii-architecture-patterns.
People also visit
architecture-patterns
Clean Architecture, Hexagonal Architecture and Domain-Driven Design
error-handling-patterns
Robust error handling with exceptions, Result types and graceful degradation
architecture-designer
High-level architecture with ADRs, Mermaid diagrams and database selection
iii-architecture-patterns FAQ
When should an agent use this skill?
When the task is larger than one function or trigger and needs a whole backend architecture.
What is a durable workflow here?
Functions chained through named queues, with progress kept in state, and retries and a dead-letter queue for failed steps.
What does the agentic backend pattern do?
Gives each AI agent its own function and passes work between agents through queue handoffs and shared state.
How does event-driven CQRS work in iii?
Command functions publish events to an event log in state, and subscribe triggers update the projections on their own.
How do I install it?
Run npx skills add https://github.com/iii-hq/iii --skill iii-architecture-patterns.
What do the security audits show?
Gen Agent Trust Hub, Socket and Snyk all pass.
What are the best iii-architecture-patterns alternatives?
Popular alternatives to iii-architecture-patterns include architecture-patterns, error-handling-patterns and microservices-patterns. See all iii-architecture-patterns alternatives