Module 4: API Design & Contract Evolution
This page aggregates the generated reference routes used by the learner-facing module.
- Semester:
semester-07-architecture-ddd - App:
architecture
Read only if stuck
- Geewax: What are web APIs?
- Geewax: What are resource-oriented APIs?
- Geewax: Expressive and simple
- Geewax: Predictable
- Geewax: What are API design patterns?
- Geewax: Why are API design patterns important?
- Geewax: What makes a name good
- Geewax: Bad names case study
- Fundamentals: Defining software architecture
- Geewax: What is resource layout?
- Geewax: Types of relationships
- Geewax: Entity relationships
- Geewax: References vs inline, anti-patterns
- Geewax: Anti-patterns -- resources for everything / inline everything
- Geewax: Which methods, idempotence, GET
- Geewax: List
- Geewax: Create and update
- Geewax: Delete
- Geewax: Partial update motivation
- Geewax: Page size
- Geewax: Page tokens
- Geewax: Offsets-and-limits anti-pattern
- Geewax: Filtering structure
- Geewax: Filter syntax 1
- Geewax: Filter syntax 2
- Geewax: Filter syntax 3 and tradeoffs
- Geewax: Custom methods motivation
- Geewax: Custom methods overview, side effects
- Geewax: Resources vs collections, tradeoffs
- Geewax: LRO motivation
- Geewax: LRO overview
- Geewax: LRO resolution
- Geewax: LRO error handling and monitoring
- Geewax: LRO canceling and exploring
- Geewax: Rerunnable jobs
- Geewax: Batch collective operations motivation
- Geewax: Batch atomicity
- Geewax: Batch get / create
- Geewax: Import / export
- Geewax: Import/export consistency
- Geewax: Request deduplication / idempotency
- Geewax: Exponential back-off
- Geewax: Retry-After and tradeoffs
- Fundamentals: Monolithic vs distributed architectures
- Fundamentals: Event-driven architecture style
- Learning DDD: Event-driven architecture
- Learning DDD: Types of events
- Learning DDD: Cooperation to conformist
- Learning DDD: Anticorruption layer
- Learning DDD: Model translation
- Geewax: What is compatibility?
- Geewax: Backward compatibility part 1
- Geewax: Backward compatibility part 2
- Geewax: Backward compatibility part 3 and implementation
- Geewax: Perpetual stability
- Geewax: Agile instability
- Geewax: Semantic versioning and tradeoffs
- Geewax: Granularity vs simplicity
- Geewax: Happiness vs ubiquity
- Geewax: Soft deletion motivation
- Geewax: Deleted designation
- Geewax: Expunging and effects
- Geewax: Soft delete across versions and tradeoffs
- Fundamentals: Monolithic vs distributed