Twitter distributes config files across their entire fleet (hundreds of thousands of machines) using git and a cron job. Commit your config change, wait a few minutes and there it is.
That's not exactly how that worked - configuration files and build artifacts were delivered by either puppet/ansible or via Murder (bt-style p2p). If there was cron involved, it was to schedule starting the puppet client on the node. The puppet manifests and every project's source was in git, but nothing went directly from git to a machine (unless internal tooling regressed dramatically after 2013).
jfray2k22|3 years ago
Source: also former Tw (2008-2013)