architect-data-platform

Define Braze data platform architecture across unification, activation, and distribution layers.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-data-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-data-platform
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-data-platform
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-data-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Braze Data Platform Architecture provides a coherent blueprint for connecting data unification, activation, and distribution so architects can reason about topology, data flow, and integration patterns.

Core Features & Use Cases

  • End-to-end architecture: three layers (Data Unification, Data Activation, Data Distribution) with clear responsibilities.
  • CDI integration and warehouse ingestion guidance, including delta-sync patterns and zero-copy options.
  • Use cases include platform design for new Braze deployments, migrations, and scale-out scenarios while respecting operational constraints like dummy-user blocks.

Quick Start

Outline Braze data platform topology and end-to-end data flow for your project.

Frequently Asked Questions about architect-data-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to architect a Braze data platform for end-to-end data flow?

A Braze data platform architecture uses a three-layer blueprint covering data unification, activation, and distribution to map topology and integration patterns. This structure defines clear layer responsibilities for seamless end-to-end data flow.

How does Braze CDI delta-sync work during warehouse ingestion?

Braze CDI delta-sync integration enables efficient warehouse ingestion by only transferring changed data. This pattern respects operational constraints and supports zero-copy options to optimize data distribution and activation.

How do I handle dummy-user blocks when designing Braze data activation?

Handling dummy-user blocks in Braze data activation requires mapping operational constraints during platform design. The architecture blueprint addresses this by defining specific data unification and distribution rules to prevent invalid profiles.

Can I use this Braze data platform architecture for migrations and scale planning?

This Braze data platform architecture supports new deployments, migrations, and scale-out scenarios. It targets architects during platform design to reason about partner integrations and data topology without scaling constraints.

What distinguishes the three layers in Braze data distribution and unification?

The three layers distinguish responsibilities across data unification, data activation, and data distribution. Separating these functions allows architects to reason about specific integration patterns, CDI delta-sync, and partner data flows independently.