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.

event-driven-design

Design event and message contracts across services, including event meaning, schema evolution, ordering and partitioning, delivery and idempotency, replay, retention and failure handling. Use when a change publishes or consumes events, introduces asynchronous integration or alters an existing event contract; not for broker installation or cluster operations.

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.