Movement — how data flows between systems

Interconnection

3 open standards for Interconnection in a modern data architecture, each with an opinionated judgement: Adopt, Situational, Assess, or Caution.

Start with HTTP.

Adopt 1 standard

The standard to reach for in new work. Proven, multi-vendor, clearly the default for its slot.

  • HTTP — Hypertext Transfer Protocol

    Universal application transport; nobody decides to use it.

    IETF

Situational 1 standard

The right answer in some contexts but not others. Pick deliberately based on the constraint.

  • Delta Sharing — Delta Sharing Protocol

    Cross-org sharing without copies; well-defined niche.

    Linux Foundation (donated by Databricks)

Caution 1 standard

We'd avoid it for new work — superseded or fading, but still encountered in existing systems.

  • FTP / SFTP — File Transfer Protocol / SSH File Transfer Protocol

    Unencrypted FTP is unsafe for new work; SFTP-only as a last resort when partners can't speak HTTP APIs.

    IETF

More in Movement

Movement covers how data flows between systems.

See Interconnection in context

These standards are one panel of the interactive Data Landscape, which maps every open standard a modern data architecture is built on. The underlying data is a single JSON file; disagree with a judgement? Open an issue.