Devops for Growth

Overview Here at FMP, we practice trunk-based development, with changes committed to the main trunk being deployed by our continuous integration server onto our acceptance, integration and finally production servers. We commit to trunk multiple times daily, and provided that the deployment pipeline is green, that also means we deploy those changes to our production servers multiple times daily.

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

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!