Data federation
Reading data that lives in another system as if it were local — by federating the query, by copying the rows, or by caching what was read. Three different answers to one question, and the choice is about how stale you can afford to be.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Overview
Represents another CAP application's exported entities as SAP HANA synonyms in the consuming application's schema, so a consumption view reads the provider's tables in place and no row is copied; access to the provider is read-only.
Shows service-level replication as application code in the Data Federation guide: about forty lines in the xtravels sample that turn each @federated entity into a table, schedule a replicate handler with the runtime's scheduling API and upsert the rows newer than the local maximum of modifiedAt. The runtime supplies the annotation, the scheduling and the remote query; the loop is the application's own.
A Node.js coverage assessment has not been written. View all flavors
Declares on a consumption view whether a remote entity is delegated to at query time, replicated into a local table on a schedule through cds-data-pipeline, or cached; the handlers and the query translation are registered at boot from the annotation.
Runs a scheduled READ, MAP, WRITE pipeline that copies an entity from an OData, REST or CAP source into a local table or a remote OData target, with delta modes, retry and a management API.
A Node.js coverage assessment has not been written. View all flavors
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysReplication by a covered CAP application moves data from an SAP product into a non-SAP product.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
Section 1 restricts mass extraction to a non-SAP product and states a scoped interoperability exception. That boundary is central to a replication design and must be checked against the actual use.
SAP Developer License Agreement 3.2 CAP →Artifacts
Content
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:replication- JSON
- /capabilities/replication.json
- MCP
- Connecting an agent