News for hackers. Stuff that matters.
Re:Using Kubernetes to rethink your system architecture and ... by MichaelMoser123 on Sunday May 23, 2021 @02:39PM (#27257397)
Did the stackoverflow architecture change significantly from this series of posts? (seems to mentioning 2016-2019) [1] The article mentions a rewrite, but it wasn't very specific on the scope of the rewrite, and what kind of stack they are using now.

I thought they were running their own farm with most of the action on IIS with ASP.net and MSSQL, and some elasticsearch for search.

[1] https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar...

Re:Using Kubernetes to rethink your system architecture and ... by jimminy on Sunday May 23, 2021 @02:54PM (#27257531)
The article is a guest post from individuals that work at Pusher[1], about architectural decisions they made for their products and services.

I also thought it would be about StackOverflow until they started mentioning all the Pusher related products.

[1] https://pusher.com

Re:Using Kubernetes to rethink your system architecture and ... by MichaelMoser123 on Sunday May 23, 2021 @03:29PM (#27257803)
Oh, thanks. Skipped that emtirely. (Too much HN for me)
Re:Using Kubernetes to rethink your system architecture and ... by papito on Thursday May 27, 2021 @05:44AM (#27300982)
No, Stackoverflow architecture is still a simple server farm with aggressively maintained code and a lite SQL ORM that lets them to highly optimize queries. One of the architects talked about it on their pod a few weeks ago. She mentioned explicitly how they don't jump on new hotness and keep it classic, maintainable, and highly performant without spending tens of millions of dollars on FAANG alumni who seem to think that every shop needs a Google infrastructure because THIS IS THE WAY.