How Quasa.rs utilizes Blue/Green Deployments

  • If the deploy goes badly, we can always flip the floating IP back to the original box while keeping the bad deployment in an unaltered state to investigate.
  • Both our “production” and “staging” environments take turns receiving real production traffic, assuring that our staging environment will never be stale or deviate from production.
  • In our case, we can run migrations and verifications on the box we deployed to without interrupting user traffic.
  • If I suddenly need scale, I can always swap out the floating IP with a load balancer and serve requests to both environments (does require manually asserting that both environments have the same deployment version which is less-than-ideal).
  • For roughly $15/month I can have an active-active setup.
Martin Fowler’s diagram of blue/green deployments

--

--

--

Software Engineer. 70% of my body is made of code.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

A business point of view ….

Combating Alert Fatigue with a Global Issue Dashboard

Using globals and locals from STATA in Python

Generating submasks of a given mask

The basics of code design everyone should know

Python Logging

Symfony Station Communique — 19 November 2021. A Look at Symfony and PHP News.

Symfony Station logo

Product-Market fit and what’s next for the agile adventure platform: Investor Update #4 part 2

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Patrick Brown

Patrick Brown

Software Engineer. 70% of my body is made of code.

More from Medium

Factory Method Pattern vs Simple Factory

What to do if your UAT and Prod environment are different

A brief introduction to mutation tests

The flat file in webMethods with Demo.