Person
FabianBerr
Capabilities
Contributes to
CachingCAPCachingHolding the result of an expensive read so the next one is cheap. This spans four different things people call caching — HTTP response caching, query result caching, remote service response caching, and application-level memoisation. They are not interchangeable, and picking the wrong one is the usual cause of stale-data bugs in multitenant apps.TelemetryCAPTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.
Entries
Group by
EntrySignals
Contributes to
cds-cachingcds-cachingA caching plugin for CAP covering queries, requests, function results and remote service responses, through a read-through API or @cache annotations, with HCQL and MCP support.independent, cap
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
CAP caching plugin for query results and remote service responses
Writing and topics
IN TOPICS
Building onedevatlas: the idea, the back-and-forth with AI, the wrong turns, and an orb who lost his permanent spot in the atlas.
Details
For your agent
- Ref
actor:fabianberr- JSON
- /actors/fabianberr.json
- MCP
- Connecting an agent