Ephemeral Environments Across Your Team

Ephemeral Environments Across Your Team

From enabling a sales engineer to demo a new feature to helping a product person give feedback, ephemeral environments allow your teams to collaborate across your application lifecycle. Since ephemeral environments are lightweight and easily shareable, they simplify many of the barriers that plague cross-team communications, resulting in a faster, smoother workflow.

Developers Working With Developers

During the code review process, developers will look at peers' code and test any new features. To do this, they need to tear down their local environments in order to build another developer’s environment. However, with ephemeral environments:

Developers Working With Product Team

After developers create a new feature, they’ll want to run it past someone on the product team, as they often need feedback and may have additional questions. However, when working on an assigned ticket, developers may also require someone on the Product team to review the WIP feature. With ephemeral environments:

QA Working With Developers

QA teams review features before they reach production and communicate the results of their assessments back to the developers. Ephemeral environments provide a tighter feedback loop. For example:

Sales Working With Developers

Sales teams will need to demo features to potential customers. However, they may run into blocks if a demo environment is in use or in a state of repair. Additionally, a customer may request to see a new feature in action, but the team may not have a steady way to host it. Ephemeral environments help by:

Content Contributors

nbeck415 on GitHub
bueller on GitHub