Just the pic, archived: https://web.archive.org/web/20210907091921/https://pbs.twimg...
“You don't need this overengineered goo for your project.”
41–50 of 107 posts
Re: “You don't need this overengineered goo for your project.”
#42Earlier quoted context omitted.
And if they don't like your politics, they simply pull the plug.
You mean morally indefensible politics and misinformation propaganda? Oh no. Anyway. I mean these politics are pushed by rich Americans and foreign interests, surely they have the means to start their own hosting platform. It's the same that advocate in favor of businesses rejecting customers because of free market.
I'm not saying Amazon shouldn't be free to do that. Just that you should think twice about trusting them with your business.
No further comment on the specific political content - those sensibilities can change. Can your business adapt quickly enough?
Re: “You don't need this overengineered goo for your project.”
#43I love these Twitter takes. They say something to get attention but if you look at it for more than a second it's.. it's just nothing data Comparing a troubleshooting guide to running a site on a couple of servers is a bit too different for me. Compare it to a troubleshooting guide for those two servers, let's see how they stack up. No using any "ask {specific person}" either Don't get me wrong, kubernetes is overkil…
Here's the stats on Stackoverflow https://stackexchange.com/performance 1.3 billion page views per month, 9 web servers, 4 sql servers Stackoverflow is notable because they went down the C#/MVC/SQL Server route from the start, which meant much better performance per server. Thats why they make an interesting counterexample to the usual way...
> Stackoverflow is notable because they went down the C#/MVC/SQL Server route from the start, which meant much better performance per server
And also notable because everything is under an expensive license, so big performant servers is the cheaper option.
Edit: everything = Windows servers for their .NET app ( apparently in the process of migrating to .NET Core) and SQL Server
Re: “You don't need this overengineered goo for your project.”
#44That’s not an architecture diagram though, so it doesn’t represent the complexity at all. I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.
When I first saw it K8S reminded me a lot of systemd. I wouldn't be surprised if over the next few years each grow the features of the other.
That sounds logical as they kind of perform the same tasks with the difference being that systemd manages workloads on a single system and k8s manages workloads on a cluster.
Re: “You don't need this overengineered goo for your project.”
#45recently facing the dilemma of choosing between k8s vs something more basic. Features that seemed to be advocating for k8s were not server provisionning, but instead : log management, easy setup of blue/green & canary deployment, not having to restart a vm upon new code deployment, etc... How would you do those things as easily with other techs ?
Nomad all the way. It's much easier and lighter than Kubernetes, but it does 3/4 of what Kubernetes does. The ecosystem is much lighter but depending on your needs it could be entirely sufficient.
I've written about Nomad vs k8s on my blog if that might interest you:
https://atodorov.me/2021/02/27/why-you-should-take-a-look-at...
And I've also written about some common things, like Traefik for ingress, Loki for logs, etc. to supplement the pretty complete Hashicorp tutorials.
Re: “You don't need this overengineered goo for your project.”
#46Earlier quoted context omitted.
Exactly. That twitter thread is just pure rage based on no data. Sum up resources from that page - we are talking around 6500GB* of RAM worth of servers. That is no homelab. * 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.
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 .
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.”
#47That’s not an architecture diagram though, so it doesn’t represent the complexity at all. I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.
100% and one of the great things about k8s is that this diagram applies to essentially any application. Standardisation is awesome.
Proper standardization is awesome. De facto, corp-owned standarization not so much.
Re: “You don't need this overengineered goo for your project.”
#48Earlier quoted context omitted.
Here's the stats on Stackoverflow https://stackexchange.com/performance 1.3 billion page views per month, 9 web servers, 4 sql servers Stackoverflow is notable because they went down the C#/MVC/SQL Server route from the start, which meant much better performance per server. Thats why they make an interesting counterexample to the usual way...
> Stackoverflow is notable because they went down the C#/MVC/SQL Server route from the start, which meant much better performance per server And also notable because everything is under an expensive license, so big performant servers is the cheaper option. Edit: everything = Windows servers for their .NET app ( apparently in the process of migrating to .NET Core) and SQL Server
what do you mean by saying "everything"? just SQL Server?
Re: “You don't need this overengineered goo for your project.”
#49Earlier quoted context omitted.
> Stackoverflow is notable because they went down the C#/MVC/SQL Server route from the start, which meant much better performance per server And also notable because everything is under an expensive license, so big performant servers is the cheaper option. Edit: everything = Windows servers for their .NET app ( apparently in the process of migrating to .NET Core) and SQL Server
what do you mean by saying "everything"? just SQL Server?
Technically Windows licences, too, but maybe they migrated to Linux with their switch to .NET (Core).
Re: “You don't need this overengineered goo for your project.”
#50Earlier quoted context omitted.
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 .
Because they're constrained by Windows and Microsoft licensing, scaling out was never an easy option for them.
>Because they're constrained by Windows
How? didn't they migrate to .NET Core?