Architecture & Design Patterns

Defines serverless architecture patterns for event-driven workloads.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/ftnilsson/agent-registry --skill architecture-design-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture & Design Patterns
Source: https://github.com/ftnilsson/agent-registry/tree/main/serverless/skills/01-architecture-and-design-patterns
Command: npx skills add https://github.com/ftnilsson/agent-registry --skill architecture-design-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Serverless architectures can become complex to design and maintain as systems scale. This Skill provides a structured set of patterns and best practices to help teams build scalable, event-driven applications with clear boundaries and reliable behavior.

Core Features & Use Cases

  • Event-Driven Design: treat all function invocations as reactions to events and design for eventual consistency.
  • Choreography vs Orchestration: guidance on when to use independent event reactions versus managed workflow engines.
  • Composition Patterns: function chaining, fan-out/fan-in, async HTTP, and more for durable, scalable pipelines.
  • Bounded Contexts: organise services into isolated domains with clear data ownership and integration via events or APIs.
  • Anti-patterns & Best Practices: avoid monolith functions, ensure retries, dead-letter queues, and proper observability.

Quick Start

Identify a spiky workload and apply an appropriate serverless pattern to implement a resilient, event-driven workflow.

Frequently Asked Questions about Architecture & Design Patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between choreography and orchestration in event-driven serverless architectures?

Choreography uses independent event reactions for decentralized workflows, while orchestration uses managed workflow engines to control distributed services. Choosing between them depends on your need for explicit state management versus autonomous event reactions.

How do I design serverless data processing pipelines for spiky workloads?

Design serverless data processing pipelines using composition patterns like fan-out/fan-in and function chaining. These event-driven patterns optimize cost and scalability by treating function invocations as reactions to events while ensuring durable execution.

When should I use bounded contexts in serverless architecture?

Use bounded contexts in serverless architecture to organize services into isolated domains with clear data ownership. This pattern ensures reliable behavior in event-driven workloads by integrating distributed services via events or APIs.

How do I handle errors and ensure observability in event-driven workloads?

Handle errors in event-driven workloads by implementing retries and dead-letter queues. Ensure proper observability across distributed services to monitor function invocations and maintain reliable behavior during spiky workload processing.

What are common serverless anti-patterns for background jobs?

Common serverless anti-patterns for background jobs include building monolith functions and neglecting eventual consistency. Avoid these by applying composition patterns and ensuring robust error handling with proper retries and dead-letter queues.

Can I apply serverless patterns to API front-ends and async HTTP processing?

Yes, you can apply serverless patterns to API front-ends using async HTTP and function chaining. These composition patterns create durable, scalable pipelines that optimize cost and resilience for distributed event-driven workloads.