Under the hood of the Delta Sharing protocol
How a Delta Sharing server, dsserv, implements the open-source Delta Sharing protocol for zero-copy sharing: Delta tables ingested, governed and streamed live from local S3-compatible storage into cloud consumers such as DatabricksDatabricksA unified data and AI platform. sap-bdc-mcp-server creates the Delta shares it registers with SAP Business Data Cloud in a Databricks workspace.. Neither the server nor the protocol is an atlas entry; the edges are to data federationData federationReading 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.SAP and community, narrow by design, the concern zero-copy sharing answers, and to object storageObject storageStoring application files as objects in a bucket or container backed by a cloud storage service. Connecting a file to a business record is the separate Attachments concern.SAP only, where the tables sit, and the abstract names no SAP product. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Philipp Nell, written here from SAP's abstract; the recording is not yet published.
Where it sits
Properties
About this work
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
Graph
Source
History
- Entered the atlasDiscovered via SAP TechEd — session catalogue · build/teched.
For your agent
- Ref
content:teched-2026-ct1163- JSON
- /content/teched-2026-ct1163.json
- MCP
- Connecting an agent