0 views collected around this technical thread.
This article explains how to enable Vue Devtools on production sites by injecting a script via the browser console, demonstrates the process with an Element‑UI example, and provides Vue 3 adaptation code for debugging live Vue applications.
The article uses a real‑world raid‑rebuild incident to illustrate why operations teams must understand change background, schedule, and risk, act as project managers, follow a formal change process, and treat production environments with utmost respect.
This guide explains how Rust’s ownership model, zero‑cost abstractions, async/await, and built‑in safety features enable teams to build high‑performance, reliable backend services at scale, while sharing practical code examples and lessons learned from real‑world production deployments.
This guide walks you through planning, configuring, and deploying a production‑grade Kubernetes cluster with high performance and availability, covering host planning, HA load balancing with keepalived and HAProxy, Harbor setup, node initialization, and essential system tweaks, all illustrated with ready‑to‑run code snippets.
This article warns developers about several Redis commands—such as KEYS, FLUSHDB/FLUSHALL, SAVE/BGSAVE, and DEBUG SLEEP—that can cause performance degradation, data loss, or security issues in production environments, and encourages careful usage to avoid serious operational risks.
This article recounts how a production database deadlock was uncovered during testing, explains the use of the EasyBI monitoring tool to collect and visualize error and claim statistics, and shares the step‑by‑step configuration, analysis, and lessons learned for preventing similar issues in future systems.
This article outlines the most common production failures—including network, server, database, software bugs, security vulnerabilities, storage, configuration errors, and third‑party service issues—and provides detailed steps for detection, investigation, and resolution to ensure system stability and reliability.
This guide outlines the most common production failures—including network, server, database, software, security, storage, configuration, and third‑party service issues—and provides detailed steps for detecting, diagnosing, and resolving each type to maintain system stability and reliability.
This article outlines nine typical problems that arise when executing SQL scripts in production—such as missing scripts, syntax errors, wrong order, timing issues, wrong database selection, long‑running updates, lack of rollback, missing indexes, and field renaming—and provides practical solutions to prevent each pitfall.
This translated article shares 42 practical lessons from Mahesh Balakrishnan’s experience building a production database, covering customer focus, project management, design principles, code review, strategy, observability, and research practices for reliable infrastructure development.
This translated article shares 42 practical lessons drawn from Mahesh Balakrishnan’s experience building a production database, covering customer focus, project management, design principles, observability, research, and strategic thinking to help engineers and managers create reliable, scalable infrastructure.
The article examines why SRE teams experience overload due to high incident response demands, analyzes contributing factors such as production issues, alert volume, and manual processes, and proposes comprehensive mitigation steps including better testing, load management, and proactive error detection to reduce on‑call burden.
This article compares traditional Python web frameworks with modern asynchronous alternatives, presents benchmark data showing Sanic’s superior speed, explains the benefits of async I/O, and discusses Sanic’s ecosystem, production readiness, documentation, and community support for developers seeking high‑performance backend solutions.
This article recounts a two‑year journey of migrating from Ansible‑managed EC2 deployments to Kubernetes, detailing the motivations, migration strategy, operational challenges, tooling choices, resource management, security, cost considerations, and the development of custom controllers and CRDs to run production workloads reliably.
This article demonstrates how the open‑source Java diagnostic tool Arthas can be employed in various production scenarios—such as CPU spikes, class‑loading conflicts, method‑level monitoring, performance bottlenecks, and hot‑code replacement—to rapidly locate and resolve runtime problems without restarting services.
This article walks through a real‑world production incident involving intermittent interface timeouts, demonstrates how tracing with SkyWalking and log analysis revealed a downstream service problem, explores GC log diagnostics, uncovers misconfigured c3p0 connection‑pool settings, and shares practical lessons for Java backend performance tuning.
The article recounts a detailed troubleshooting process—including data verification, code review, DBA assistance, local debugging, environment comparison, logging, packet capture, service restarts, async‑to‑sync changes, load testing, and Kafka partition tuning—that ultimately identified a Kafka partition bottleneck as the cause of a sudden data‑volume decline after a new feature went live.
The article explains how traditional IT silos hinder rapid incident response, outlines common symptoms of poorly managed applications, and argues that adopting DevOps—supported by cloud‑native infrastructure, automation, and shared responsibility—delivers higher transparency, employee autonomy, operational quality, and customer satisfaction.
This article examines production JVM memory architecture, explains GC log generation and analysis, details the ParNew + CMS collector behavior, and provides practical parameter tuning recommendations to optimize heap size, young generation, and garbage collection for stable Java applications in production environments.
The article argues that while rapid prototyping with HTML, CSS, and JavaScript is essential for testing ideas, developers should never carry prototype code into production, emphasizing speed over semantics during prototyping but insisting on quality, performance, and accessibility for final releases.