Data 360 Ingestion & Federation Pattern Selector

Experimental

Recommend the best ingestion or federation architecture pattern for Data 360 across latency, volume, governance, and analytics requirements.

Example Output E-commerce platform — 50M events/day, near-real-time dashboards, strict governance, external data lake

Streaming Ingestion

Recommended Pattern

Batch + Streaming Hybrid Alternative pattern Medium-High Cost profile < 1 min Freshness

Key Findings

  • Streaming ingestion meets sub-minute freshness requirement for operational dashboards at high volume.
  • External data lake enables zero-copy federation for historical analytics — avoids duplicate ingestion costs.
  • Strict governance requires event-level audit trail; streaming connector with DLP tagging satisfies this.

Streaming ingestion for operational events + zero-copy federation for analytics. Switch to hybrid pattern only if cost becomes the primary constraint at 2×+ current volume.

Run your own analysis below

Related Tools

Salesforce Architecture

Salesforce Credits Estimator

Estimate Salesforce Data Cloud and AI consumption credits to plan platform usage.

Salesforce Architecture

Data 360 Home Org Provisioning Advisor

Evaluate Data Cloud One, existing-org, and dedicated-org provisioning strategies for Salesforce Data 360.

Salesforce Architecture

Data 360 Multi-Org Strategy Simulator

Simulate independent, shared, and hybrid Data 360 multi-org strategies across governance and reporting needs.

Tool Model Metadata

Model Version:
1.0
Last Reviewed:
Mar 2026
Decision Model:
Salesforce Data 360 Architecture Decision Engine

Methodology

Salesforce Data 360 Ingestion and Federation Model

Selects ingestion and federation patterns based on latency, data volume, integration topology, and lifecycle constraints.

Framework Alignment

Related Articles

Model Change Log

  • v1.0

    Mar 2026

    Initial release.