Skip to main content

Custom Actions: When CRUD Does Not Fit

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface​

  • Open learner-facing unit
  • Curriculum path: content/curriculum/architecture/semester-07-architecture-ddd/module-04-api-design-contract-evolution/concepts/cluster-03-beyond-crud-actions-events-async/07-custom-actions-on-resources-primary.md
  • App: architecture
  • Semester: semester-07-architecture-ddd
  • Module: module-04-api-design-contract-evolution
  • Unit kind: concept
  • Curation level: module_curated

Learning objectives​

  • Explain Custom Actions: When CRUD Does Not Fit as a contract and evolution problem, not just an endpoint-shape or schema-format decision.
  • Use Custom Actions: When CRUD Does Not Fit to reason about compatibility, versioning, lifecycle cost, and the blast radius of public interfaces.
  • Use api-design-patterns to connect the learner page to contract design, compatibility strategy, and API governance decisions.

Prerequisites​

  • Comfort with modular boundaries and bounded contexts, because APIs are where those boundaries become explicit contracts.

Source books​

  • api-design-patterns

Source routes​

Api Design Patterns​

  • /books/api-design-patterns via Geewax: Custom methods - motivation, why not just standard methods, Geewax: Overview and side effects, Geewax: Resources vs collections, stateless, final definition, tradeoffs

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

  • Microsoft REST API Guidelines (official_docs_companion) - Anchors API contract thinking in a real, widely used design standard rather than intuition.
  • Zalando RESTful API Guidelines (optional_deep_dive) - Useful for comparing how different organizations encode compatibility and lifecycle tradeoffs.

AI companion modes​

  • Explain simply
  • Socratic tutor
  • Challenge my understanding
  • Diagnose my confusion
  • Connect forward / backward

Source-of-truth note​

This teaching unit is learner-facing guidance. Its canonical source backbone is the referenced book api-design-patterns, and outside material should only clarify or strengthen that backbone.