Skip to content

joao-aires/backend-development

v0.3.0MIT

Framework-independent service authority, state, durable work, failure, architecture pattern selection, HTTP and GraphQL contracts, event-driven integration and distributed-systems reasoning.

architecture-patterns

Select and compare backend architecture patterns — modular monolith, layered, hexagonal/ports-and-adapters, clean/onion, CQRS, event sourcing, microservices and serverless — by the forces that justify them, their costs and migration path. Use when an architecture proposal or option comparison needs pattern candidates, a fit check or a tradeoff review; the architecture decision, service behavior, event contracts and cross-service failure reasoning stay with their owning capabilities.

Read SKILL.md at the source

Pinned to revision c37715f7cf0d, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.