ComposableStack.AI CDP
Back to agent
Recommendationrecommendation.aep-heavy-enterprise-adopt-edge-node-pattern

AEP-heavy enterprise — adopt AEP-as-edge-node over full displacement or status quo

For a large enterprise with AEP as the incumbent CDP, a matrixed org structure splitting IT/Marketing accountability, and a data-warehouse team hitting AEP's export and query guardrails, the recommended direction is pattern.aep-as-edge-node: move audience computation and identity resolution to the CDW, keep AEP as a downstream activation consumer fed by reverse-ETL. This relieves the guardrail pressure driving the evaluation without the cost and political friction of displacing AEP outright.

confidence 82%v1reviewed Aug 25, 2026recommendation, aep, composable, enterprise, edge-node, reverse-etl, cdw

AEP-heavy enterprise — adopt AEP-as-edge-node over full displacement or status quo

When a large enterprise (typically >$1B revenue, >500K profiles in AEP) has AEP as the incumbent CDP under matrixed IT/Marketing governance, and a cloud data warehouse team has grown organically and is now hitting AEP's export, query, and batch-scheduling guardrails, this recommendation names the middle path between the two extremes the organization is usually weighing.

Why this recommendation exists. archetype.aep-heavy-enterprise-evaluating-composable documents the trigger pattern in detail: egress limits, ad-hoc query timeouts, and batch-activation scheduling congestion are discovered during production scale-up, not anticipated at purchase time. pattern.aep-as-edge-node is the archetype's own stated recommended direction — this node makes that traversal path explicit in the graph and states the tradeoff alongside the alternatives.

What this recommendation is not. It does not recommend ripping out AEP, and it does not recommend ignoring the guardrail friction as a configuration problem. Both of those are the alternatives, not the default. The edge-node pattern is the default because it honors the existing AEP investment (activations, destinations, integrations already built) while moving the data-intensive work to where compute is unconstrained.

Scope limitation. This recommendation assumes a CDW team already exists (tech-dim.dev-team.backend-data-warehouse) — without one, there is no destination for CDW-computed audiences and the edge-node pattern has nothing to move work to. Organizations without a CDW team should first evaluate whether an enterprise packaged CDP replacement or continued AEP-only operation is the realistic near-term path.

Sources

Related

This node →

  • applies-to-domainorg-dim.org-chart-type.matrixed-enterprise— OC-133. Recommendation triggered by archetype.aep-heavy-enterprise-evaluating-composable, which fires on org-dim.org-chart-type.matrixed-enterprise (applies-when edge present 2026-05-10). Propagates the domain scope to the recommendation, keeping the OrgDimension -> Archetype -> Recommendation traversal path consistent, matching the convention already used for recommendation.salesforce-ecosystem-cdp-deepen-or-composable-augment.

← Referenced by

  • recommendsarchetype.aep-heavy-enterprise-evaluating-composable— OC-133. The archetype's own body already names pattern.aep-as-edge-node as its recommended direction; this standalone recommendation node makes the archetype -> recommendation traversal path explicit, matching the established convention (archetype.salesforce-ecosystem-enterprise-evaluating-cdp -> recommends -> recommendation.salesforce-ecosystem-cdp-deepen-or-composable-augment; archetype.healthcare-provider-hipaa-performance-marketing -> recommends -> recommendation.hipaa-tracking-layer-phi-suppression). Closes one of the three OC-133 coverage gaps.