0 views collected around this technical thread.
This article demonstrates how to embed a hidden Facebook Like button that automatically registers likes as the user moves the mouse, using HTML, CSS positioning, JavaScript event handling, and the Facebook SDK, while keeping the element invisible to the user.
The article explains how Facebook abandoned Git for a heavily customized Mercurial and how Google, facing similar monorepo scaling problems, built its own version‑control system called Piper, illustrating the challenges of managing ultra‑large codebases at internet giants.
This article explains Facebook’s internal configuration management system, detailing how tools like Configerator treat configuration as code, support version control, automated validation, large‑scale distribution, UI editing, and canary testing to prevent errors and streamline deployment across services.
The article explains Facebook’s autonomous integration testing infrastructure, detailing how it abstracts services, employs fuzzing, mock services, and record‑and‑playback techniques to enable scalable, isolated testing of backend microservices while minimizing friction and ensuring reliable software delivery.
This article analyses seven years of Facebook mobile development data to show how increasing release frequency can coexist with stable engineer productivity and unchanged software quality, using metrics such as daily code changes, commit frequency, bug severity, crash rates, cherry‑picks and launch‑blockers.
This article examines Facebook's mobile continuous deployment approach, detailing how increased release frequency, automated pipelines, and a clear separation between development and release engineering have allowed weekly Android and iOS updates without sacrificing software quality or developer productivity.
The article details Facebook’s multi‑year effort to migrate its heavily customized MySQL 5.6 deployment—including the MyRocks storage engine—to MySQL 8.0, describing the technical challenges, patch‑porting strategy, replication changes, automated verification, and application validation performed during the upgrade.
The article explains how Facebook’s Shard Manager tackles large‑scale system sharding by combining stateful and stateless service deployment, consistent hashing versus sharding, fault‑as‑normal principles, replication, automated failover, load‑balancing, and elastic scaling to achieve high availability and efficient resource use.
This article explains how Facebook engineered a massive‑scale continuous delivery pipeline—evolving from manual cherry‑pick releases to a near‑continuous deployment system that safely pushes hundreds of code changes per hour to both web and mobile users worldwide.
This article explains how Facebook built a highly scalable continuous delivery pipeline for both web and mobile products, evolving from simple trunk‑based releases with cherry‑picks to a quasi‑continuous deployment model that supports thousands of engineers, rapid rollouts, and robust quality monitoring.
This paper describes Facebook's continuous deployment practice for its Android and iOS mobile apps, outlines the release workflow, presents a seven‑year data set covering commits, crashes, and issue tracking, and analyses how deployment frequency, team size, and release timing affect developer productivity and software quality.
This article examines Facebook's large‑scale configuration management system, detailing Configerator and Gatekeeper performance metrics, latency breakdowns, real‑world configuration error incidents, statistical analysis of failures, and the DevOps practices that keep the system reliable and scalable.
This article summarizes Facebook's holistic configuration management practices, presenting cultural influences, storage growth, size distribution, update frequency, change magnitude, and author collaboration statistics, while linking to a series of translated articles that explore tools such as Configerator, GateKeeper, and MobileConfig.
This article explains Facebook's MobileConfig system, detailing its architecture, challenges of mobile configuration management, pull‑based update mechanism, translation layer, and how it scales to billions of devices while reusing data‑center tools.
The article explains how Facebook uses the GateKeeper configuration system to perform safe, incremental rolling releases of new features, describing the release stages, constraint‑based switch logic, integration with external data stores, and the trade‑offs between flexibility and operational risk.
This article explains how Facebook’s Configerator system achieves scalable, reliable configuration distribution using a push model, a hierarchical Zeus tree, Package Vessel for large data, and multi‑repo Git strategies to improve commit throughput and fault tolerance.
The article outlines Presto’s high‑performance, coordinator‑worker architecture and query flow, describes YouZan’s migration from mixed Hadoop deployment to dedicated low‑latency clusters, details challenges such as small‑file handling and regex backtracking with their fixes, and previews future enhancements like Alluxio integration, session property managers, and Ranger‑based multi‑tenant isolation.
The article examines Facebook’s massive, real‑time configuration management system, describing its rapid change frequency, the engineering challenges of configuration sprawl, authoring, validation, dependency handling, and the scalable, reliable distribution mechanisms that keep billions of devices and servers consistently updated.
In 2019, IDCF organized three in‑depth DevOps case study events where participants analyzed the practices of leading companies such as Facebook, Microsoft, Etsy and others, highlighting hacker culture, automated Windows builds, and a five‑step tech transformation roadmap.
This case study examines Facebook's origins, mission, core leadership, explosive growth, business model, and especially its distinctive engineering culture—known as The Hacker Way—highlighting practices such as bootcamps, hackathons, hackamonths, information transparency, and empowerment that drive innovation and align employee performance with company goals.