52 karma · joined February 18, 2016
Same with political extremists. It's unfortunate all of this exists, but it's a side effect of freedom to self-host.
I'd challenge the idea of dedicated infrastructure per developer in the first place. There's little reason why this could not be done locally on a developer machine using Vagrant, local Kubernetes, Docker Compose, whatever.
On Linux this worked perfectly for me, but on Macs there are some (Electron?) applications which have their own idea of keybindings. Notably MS Teams. They have their own idea of keybindings and assume some kind of quertz layout. Which using neo makes typing a questionmark, which works using "layer 3 key" (caps lock) and what is "h" on querty impossible. So I end up mostly just typing :question in chat, which produces a questionmark emoticon. Talk about workarounds. Oh yeah, it does not work because Teams opens the "help" window instead.
FWIW we're in the middle of going 100 % AWS after having used a dual setup with Hetzner for base load and AWS for dynamic load. Using spot instances for base load and autoscaling groups for dynamic load proved to be competitive in machine cost with Hetzner.
Plus there's a lot less management overhead with AWS on our scale (50+ machines). And the security of VPC and IAM cannot be replicated on Hetzner. Plus as always, it's the integration of all AWS services that's hard to beat. And we really need to be multi-region anyways (5 regions and counting).
I myself have hoped for a Go rewrite of Logstash for a long time, but there are apparently no plans for this. They are creating lightweight forwarders with their *beats, though. But they are only for forwarding to ElasticSearch, not a general log pipeline processor like Logstash.
FWIW there is a thing that's like Logstash in Go, it's Heka by Mozilla. I am very fond of it, but for some reason not many people seem to be aware of it or deploy it.