Catalog
Seven things to look up, rather than seven things to read.
Nothing here is meant to be read front to back. A catalogue answers a question you already have — what does this service promise, what listens to this event, how is this run in our team, which pattern fits this problem, what does any of it look like on Quarkus. Four of them already exist in the neighbouring hubs and are linked rather than copied.
Catalogs
API
Every registered contract with its scorecard and revision history. Contract-first has to be checkable to mean anything, and this is where it is checked.
Open the API catalogue (leaves this site)C4
Context, container and component diagrams generated from one model, so the four zoom levels cannot contradict each other — or the code they describe.
Open the C4 model (leaves this site)Events
The messages that cross service boundaries — who publishes what, who consumes it, and which schema version is in flight right now.
Open the event catalogue (leaves this site)Components
Every deployed component, and for each one the call sequence of a main use case as it really executed — recorded from a run, not drawn from memory.
Open the component catalogue (leaves this site)Practices
The thirteen practices that keep a team connected, in the order a feature passes through them: event storming, DDD, story mapping, three amigos, example mapping, digital artefacts, ticket emission, grooming, BDD, ATDD, API-first, contract-first and all-in-one testing.
Read the practicesCode design
The pattern vocabulary a design conversation runs on: GoF, tactical DDD, architecture, integration and use case patterns — each with the forces that make it the right answer.
Read the patternsTesting tools
The tools that turn three practices into something a build can fail on: Microcks for contract-driven API mocking and conformance, Cucumber for executable specifications, Playwright for the browser.
Read the toolingStacks
The same practices and patterns expressed per stack — iOS, Android, Angular, Spring Boot, Quarkus and EAP — because advice that never names a framework is advice nobody can follow on Monday.
Read the stacks