Expand my Community achievements bar.

SOLVED

Best practice for creating Datastreams per development environment

Avatar

Community Advisor

What's the best practice now for creating Datastreams in relation to the development environment (i.e. development, staging, production)?

I remember that when Datastreams were first introduced, creating a single datastream would result in 3 datastreams, 1 for each development environment. All 3 datastreams retained the same datastream ID, though the development and staging ones had ":dev" and ":stage" appended to their IDs respectively.

But now, when I create a datastream, I end up with just 1 datastream. Does this mean the best practice now is to create separate datastreams -- that end up with different datastream IDs -- for each development environment?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 1

Datastreams are sandbox aware now, so it can match your AEP sandbox environments.

At a minimum 1 prod and 1 non-prod Datastream

View solution in original post

1 Reply

Avatar

Correct answer by
Level 1

Datastreams are sandbox aware now, so it can match your AEP sandbox environments.

At a minimum 1 prod and 1 non-prod Datastream