Re:“You don't need this overengineered goo for your project.”
by slooonz on Tuesday September 07, 2021 @05:03AM
(#28442581)
And yet the main point stand : they don't need K8s to manage this application running on 23 servers.
Re:“You don't need this overengineered goo for your project.”
by szszrk on Tuesday September 07, 2021 @08:19AM
(#28443773)
No one needs k8s. Bringing up their infrastructure in a k8s troubleshooting how-to was a weird thing to do in the first place. It's comparing apples and chandelier - makes no sense.
They have a typical vertically scaled infrastructure, most services have just two nodes, one active. The biggest ones are databases which in many companies are handled in "the classic way" anyway. Clearly it's not designed as microservices and doesn't need dynamic automation at all. Why on earth would they even bring k8s up in their plans?
Re:“You don't need this overengineered goo for your project.”
by OJFord on Tuesday September 07, 2021 @07:03AM
(#28443285)
And yet it wouldn't be out of place either.
Re:“You don't need this overengineered goo for your project.”
by chrismorgan on Tuesday September 07, 2021 @05:00AM
(#28442565)
Nevertheless, it is true that Stack Overflow has focused on backend performance and scaled vertically a long way, further than is fashionable. Just not so far as only using two servers for everything.
Re:“You don't need this overengineered goo for your project.”
by sofixa on Tuesday September 07, 2021 @05:36AM
(#28442770)
Because they're constrained by Windows and Microsoft licensing, scaling out was never an easy option for them.
Re:“You don't need this overengineered goo for your project.”
by mijoharas on Tuesday September 07, 2021 @09:39AM
(#28444678)
I'm curious. I saw a similar comment earlier, surely the surely windows licensing is just a drop in the bucket compared to the rest of the infrastructure costs?
I've not really looked at hosting anything on windows before, do they have unusual licensing terms in such a way that it would be a significant cost?
Re:“You don't need this overengineered goo for your project.”
by manigandham on Tuesday September 07, 2021 @08:25AM
(#28443822)
What constraints? Windows Server licenses are bought per-core and the company can easily afford plenty more. This is a non-issue.
Re:“You don't need this overengineered goo for your project.”
by sofixa on Tuesday September 07, 2021 @09:27AM
(#28444539)
But adding a new server includes having to buy new licenses, which is a consideration you don't have with OSes that under licensing. It costs extra money, and used to be per socket when their infrastructure was conceived.
Re:“You don't need this overengineered goo for your project.”
by manigandham on Tuesday September 07, 2021 @10:34AM
(#28445365)
So what? Licenses are not expensive, especially compared to all of their other costs like the dozens of staff, and paying an invoice isn't complicated. They maintain their own hardware in colocation facilities so they'll get a new license way before they even get the hardware shipped out.
Why does this make scaling out "never an easy option for them"?
Re:“You don't need this overengineered goo for your project.”
by tester34 on Tuesday September 07, 2021 @05:45AM
(#28442833)
>Because they're constrained by Windows
How? didn't they migrate to .NET Core?
Re:“You don't need this overengineered goo for your project.”
by sofixa on Tuesday September 07, 2021 @05:53AM
(#28442876)
Did they ? I must have missed it, but seems so :
https://www.infoq.com/news/2020/04/Stack-Overflow-New-Archit...
That doesn't mean they've moved away from Windows servers hosting it though.
* Maybe a bit more/less, because it's not clear to me if DB RAM is per server, or per cluster. Likely server, as on other servers. There is also no data on how big is their haproxy.