Devops for Growth
107.5K views | +0 today
Follow
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'canary release'. Clear
Scooped by Mickael Ruau
Scoop.it!

Are Canary Releases an Alternative to Testers?

Are Canary Releases an Alternative to Testers? | Devops for Growth | Scoop.it
Key Takeaways

A software Release is always associated with Risk and benefits. Business focuses on reducing risks and cashing in on benefits.
A canary release is the same as a regular release as software is being pushed to production, even if it's to a small subset of users.
A canary release doesn't guarantee detection of all issues with a small percentage of users using it as users won't be testing the app the way testers do, or may not be using all the features at a time.
In certain domains, there is a risk of reputational damage, regulatory violations and lawsuits if a canary release were to impact the user.
Given the risk associated, having a canary release capability doesn’t rule out the requirement of an exploratory tester.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

What are canary launching and dark testing?

Your software development teams want to release new product features frequently, but without endangering established production systems or confusing users who are familiar with the existing customer experience. A common answer to the challenge is dark launching and canary testing. Learn what these practices are and how they can help your organization — and your users!

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Feature Flags vs Canaries

Feature Flags vs Canaries | Devops for Growth | Scoop.it
Feature flags and canaries have different objectives despite appearing similar: Feature flags expose a specific feature to a sample set of users and then
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Les Patterns des Géants du Web – Zero Downtime Deployment | OCTO Talks !

Les Patterns des Géants du Web – Zero Downtime Deployment | OCTO Talks ! | Devops for Growth | Scoop.it

L’objectif est d’associer le mécanisme de répartition de charge (Load Balancer) à la cinématique de déploiement :

  • le load balancer déconnecte une des chaînes de production, sur laquelle est déployée la version N+1,
  • une fois cette migration effective, le load balancer dirige les utilisateurs vers cette chaîne en version N+1,
  • il déconnecte l’autre chaîne qui est ensuite mise à jour puis reconnectée à la répartition de charge
Mickael Ruau's insight:

Il existe deux points d’attention dans ce pattern de ZDD, le premier concerne les sessions utilisateurs, et le deuxième les changements de schéma de base de données.

No comment yet.