Api_design terms
Contracts between systems that need to trust each other
A well-designed API is a pleasure to integrate; a poorly designed one is a tax on every team that touches it. This category covers REST principles, GraphQL, versioning strategies, authentication patterns, rate limiting, idempotency, error responses, and the design decisions that make APIs intuitive, stable, and a joy to build against.
GraphQL Subscriptions A GraphQL operation type that opens a long-lived connection to the server and pushes real-time data updates to the client whenever a specific event occurs.
1mo ago
api_design advanced
API Contract Testing
Consumer-driven contract tests verify that a provider API matches what consumers expect — catching breaking changes before deployment, without end-to-end tests.
2mo ago
api_design advanced
Hypermedia APIs — HATEOAS
REST APIs that include links in responses — clients discover available actions from the response rather than hardcoding URLs, making APIs self-describing and evolvable.
2mo ago
api_design advanced
GraphQL Schema Design PHP 7.0+
Designing GraphQL schemas that are intuitive, evolvable, and performant — with clear type hierarchies, nullable conventions, and avoiding the N+1 query problem.
2mo ago
api_design advanced