Vezha diary #033: What does “enterprise-ready” mean in our case
Reading Time: 3 minutesVezha Weekly Entry #033: “What does “enterprise-ready” mean in our case.” We explain what worked in practice and how it affected the stability of the service.
Reading Time: 3 minutesVezha Weekly Entry #033: “What does “enterprise-ready” mean in our case.” We explain what worked in practice and how it affected the stability of the service.
Reading Time: 3 minutesIssue #032 about Vezha: “Quality standards before a big release”. Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.
Reading Time: 3 minutesIssue #031 dated 12/30/2024: “How we cleaned up technical debt without stalling development” at Vezha. About the decision of the week without unnecessary theory – only the practical result and the next focus.
Reading Time: 3 minutes#030 (2024-12-23) on Vezha blog: Less noise, more signal topic, operational impact of updates and priorities for the next iteration.
Reading Time: 3 minutesVezha Issue #029: “The Evolution of Storage and Data”. What did the team change this week, what effect did it have in production and what are we doing next.
Reading Time: 3 minutesVezha Weekly Entry #028: “Operational Reliability Above All.” We explain what worked in practice and how it affected the stability of the service.
Reading Time: 3 minutesIssue #027 about Vezha: “Evolution of the telemetry pipeline in production logic”. Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.
Reading Time: 3 minutesIssue #026 dated 11/25/2024: “Reliable Change Delivery” in Vezha. About the decision of the week without unnecessary theory – only the practical result and the next focus.
Reading Time: 3 minutes#025 (2024-11-18) on the Vezha blog: “Reliable change delivery”, operational impact of updates, and next iteration priorities.
Reading Time: 3 minutesVezha Issue #024: “Reliable Change Delivery”. What did the team change this week, what effect did it have in production and what are we doing next.
Reading Time: 3 minutesVezha Weekly Entry #023: “Reliable Change Delivery”. We explain what worked in practice and how it affected the stability of the service.
Reading Time: 3 minutesIssue #022 about Vezha: “Reliable Change Delivery”. Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.