{"ref":"content:federating-replicating-and-caching-remote-data-in-cap-part-1","page":"/content/federating-replicating-and-caching-remote-data-in-cap-part-1","json":"/content/federating-replicating-and-caching-remote-data-in-cap-part-1.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"federating-replicating-and-caching-remote-data-in-cap-part-1","title":"The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1","url":"https://community.sap.com/t5/technology-blog-posts-by-members/federating-replicating-and-caching-remote-data-in-cap-part-1/ba-p/14402349","content_type":"blog","explains":["artifact:mikezaschka-cds-data-federation"],"sources":[{"url":"https://github.com/mikezaschka/cds-data/blob/main/README.md","title":"cds-data README — lists this post under 'Blog posts (SAP Community)' as the concepts piece for the repo's plugins, and gives the post's title","checked":"2026-09-07","quote":"- [The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1](https://community.sap.com/t5/technology-blog-posts-by-members/federating-replicating-and-caching-remote-data-in-cap-part-1/ba-p/14402349) — concepts, CAP primitives, and how the plugins fit"}],"provenance":{"discovered_via":[{"source":"source:curator"}],"first_seen":"2026-09-07"},"summary":"Part one of two, and the concepts half: terminology, what CAP already does, and what a project still has to write. It fixes a vocabulary — federation is the umbrella for making remote data part of your model, delegation forwards each request to the remote at query time, replication is a scheduled copy into the local database, and caching is an option on either rather than a third strategy — which collides with CAP's own, since what this series calls replication is what the [CAP-level Data Federation](https://cap.cloud.sap/docs/guides/integration/data-federation) guide calls federation. From the ground the [Service Integration guide](https://cap.cloud.sap/docs/guides/integration/calesi) covers, it lists what is left to hand-write: cross-service $expand, navigation filters across the boundary, write forwarding, timeouts and retries, then scheduling, delta detection, backoff, a guard for two app instances sharing one schedule, idempotent writes, and knowing whether the last run succeeded. That list is why the edge to [cds-data-federation](artifact:mikezaschka-cds-data-federation) holds: the second half maps it onto @federation.delegate and @federation.replicate and says which package carries which part — annotations in [cds-data-federation](artifact:mikezaschka-cds-data-federation), the scheduled engine in [cds-data-pipeline](artifact:mikezaschka-cds-data-pipeline), response caching through [cds-caching](artifact:cds-caching) — so it is the design rationale for the annotations, not the API reference. The gap list and the plugins answering it come from the same person who maintains them; [cap-replication-demo](artifact:gregorwolf-cap-replication-demo) and SAP's xtravels sample are cited as the hand-written form of the same work. Part 2 is announced as a walkthrough of a demo application and is not covered here.","short":"Concepts of federating, replicating and caching remote data in CAP","authors":["actor:mike-zaschka"],"offers":["concepts"],"drafted_with_ai":true,"published_on":"source:sap-community"},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"unknown","evidence":"not crawled"},{"label":"Age","tier":"unknown","evidence":"no publication date"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"unknown","evidence":"no publication date to compare"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":1388,"unit":"views"},{"value":0,"unit":"comments"},{"value":9,"unit":"likes"}]},"signals":{"views":1388,"likes":9,"comments":0,"metrics_at":"2026-10-25"},"series":{"container":false,"of":2,"at":1,"parts":[{"position":1,"title":"The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1","url":"https://community.sap.com/t5/technology-blog-posts-by-members/federating-replicating-and-caching-remote-data-in-cap-part-1/ba-p/14402349","published":null,"state":"indexed","id":"federating-replicating-and-caching-remote-data-in-cap-part-1"},{"position":2,"title":"Federating, Replicating, and Caching Remote Data in CAP — Part 2","url":"https://community.sap.com/t5/technology-blog-posts-by-members/federating-replicating-and-caching-remote-data-in-cap-part-2/ba-p/14442604","published":"2026-07-17","state":"indexed","id":"federating-replicating-and-caching-remote-data-in-cap-part-2"}]},"edges":{"authors":[{"ref":"actor:mike-zaschka","name":"Mike Zaschka","json":"/actors/mike-zaschka.json"}]}}