Amir Farahanchi 🔹 موضوع این هفته از سری جلسات کامیونیتی به یکی از استراتژی‌های مهم در انتشار نرم‌افزار اختصاص داره: Canary Deployment. این روش به تیم‌های توسعه کمک می‌کنه تا نسخه‌های جدید رو به‌صورت مرحله‌ای منتشر کنن، مشکلات احتمالی رو زودتر شناسایی کنن و از بروز اختلال گسترده جلوگیری کنن.
اگه با مفاهیم DevOps، استقرار خودکار، یا مدیریت انتشار در پروژه‌های نرم‌افزاری سروکار دارید، این جلسه می‌تونه براتون مفید و قابل استفاده باشه.
📍 ارائه توسط محمدرضا پازوکی
🗓️ جمعه ۱۶ خرداد (۶ ژوئن) | ساعت ۲۰:۳۰ به وقت تهران (۱۹ اروپای مرکزی)
به دوستانی که تو حوزه توسعه، عملیات و زیرساخت کار می‌کنن هم اطلاع بدید!
A canary deployment is a software release strategy where a new version of an application is gradually rolled out to a small subset of users (the “canary”) before being deployed to the entire user base. This allows for testing the new version in a production environment while minimizing the risk of affecting the entire user base if issues arise.
Here’s a more detailed explanation:
-
1. Initial Release:A small percentage of users (the “canary”) are switched to the new version of the application.
-
2. Monitoring:The new version is closely monitored for performance, errors, and user feedback.
-
3. Gradual Rollout:If the new version performs well, the percentage of users being served by the new version is gradually increased.
-
4. Full Release:
Once the new version is deemed stable, all users are switched to it.
-
Reduced Risk:
By testing on a small subset of users, canary deployments significantly reduce the risk of a large-scale deployment failure.
-
Early Issue Detection:
Issues can be identified and fixed early on, preventing them from affecting the entire user base.
-
User Feedback:
Canary deployments allow for gathering real-time user feedback on new features or versions.
-
Faster Rollouts:
With a controlled and monitored rollout, canary deployments can be faster than traditional deployments.
The name comes from the practice of using canaries in coal mines to detect toxic gases. If the canary died, miners would know there was danger and would evacuate. Similarly, in canary deployments, a small subset of users acts as the “canary,” signaling if something is wrong with the new version.
0 مورد نقد و بررسی
