# Best practices to enforce models without failing assertions

**URL:** <https://discourse.getdbt.com/t/best-practices-to-enforce-models-without-failing-assertions/4390>\
**Category:** Archive\
**Created:** [May 20, 2022, 3:44pm UTC](https://discourse.getdbt.com/t/best-practices-to-enforce-models-without-failing-assertions/4390 "2022-05-20T15:44:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![preidy](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@preidy](https://discourse.getdbt.com/u/preidy)\
**Post date:** [May 20, 2022, 7:13pm UTC](https://discourse.getdbt.com/t/best-practices-to-enforce-models-without-failing-assertions/4390/2 "2022-05-20T19:13:42Z")

</div>

Hi, you may want to check out this discourse post about “blue/green deployment”: [Performing a blue/green deploy of your dbt project on Snowflake](https://discourse.getdbt.com/t/performing-a-blue-green-deploy-of-your-dbt-project-on-snowflake/1349)

From the post:

> What’s a blue/green deployment?  
> Blue-green deployment is a technique that reduces downtime and risk by running two identical production environments. Let’s take a website as an example — when you need to deploy a new version of your website, the new version is created in a separate environment. **After** the build is successful, traffic is routed to the new build. If anything goes wrong, you just don’t switch over the traffic

I haven’t implemented this strategy personally but it sounds like it could help you out with your usecase!

---

_[View the full topic](https://discourse.getdbt.com/t/best-practices-to-enforce-models-without-failing-assertions/4390)._