4 ms·
Maybe that’s why it’s so reliable.
by midasuni 4y ago
Maybe that’s why it’s so reliable.
- mritzmann 4y agoThought the same thing. Finding the root cause is easier when you don't have to debug dozens of abstraction layers (KVM, Containerd/Docker, Kubernetes, etc).
- siva7 4y agoOperating at this scale you can assume that all these things you mentioned do exist :)
- rvnx 4y agoIt's all public: https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure You can even get access to devops/SREs tickets (and IRC messages)
- baq 4y agoDocker? You’re probably right. K8s? Wouldn’t be so sure. Would like to hear from the horse’s mouth though. Edit: looks like it’s used. Wonder if it’s more tooling than production traffic. No time to dig further.
- tecleandor 4y agohttps://wikitech.wikimedia.org/wiki/MediaWiki_On_Kubernetes https://wikitech.wikimedia.org/wiki/MediaWiki_On_Kubernetes
- deleted 4y ago[deleted]
- baq 4y agoYou’re implying serious and useful work can be done in a stable tech stack? Preposterous. Seriously though, not a fan of php at all but the js tooling is rocket science in comparison.
- mschuster91 4y ago> Seriously though, not a fan of php at all but the js tooling is rocket science in comparison. laughs in left-pad, Webpack, Grunt, ... JavaScript tooling absolutely sucks - even for a moderate sized project, `npm install` can take many minutes, often enough because some native code has to be compiled. Webpack builds can take even longer. In contrast, with PHP you run `composer install` and it works, no bundling or whatever required.