CAP Advanced Patterns — Drafts, i18n, Audit Logging & Production Readiness

Lesson 3.4 — CAP Advanced Patterns & Production Readiness Table of Contents 1. Draft Handling 2. Localization (i18n) 3. Temporal Data & Audit Logging 4. Deployment Topologies 5. Performance Optimization Top 5 Pitfalls What to Learn Next Summary: Production CAP Java applications require mastering draft handling for Fiori UIs, localization/i18n, temporal data, deployment topologies (MTA vs Helm), and performance optimization. This lesson covers these advanced patterns with practical examples and configuration. 1. Draft Handling What is Draft? Draft enables Fiori's "edit session" pattern: a user opens an entity for editing, makes changes over multiple requests, then saves or discards. Changes are stored in a draft table until explicitly activated. User clicks "Edit" User modifies fields User clicks "Save" │ │ │ ▼ ▼ ▼ ┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐ │ DRAFT_NEW │ │ Draft table │ │ Copy draft → active │ │ creates draft│───→│ updated │───→│ Delete draft │ │