For anyone looking on this from the future, the error page has Content-Type set to text/html but literally returns the text: "The service is unavailable." and a newline character.
I know you're joking, but an SE employee (I believe it was Nick Craver, who is now a former SE SRE) mentioned on Twitter a while ago that employees use database backups and spin up local instances for exactly this reason...
The biggest tragedy is good answers to bad questions. The answer might teach you something you never knew before, but if the question is judged harshly it might get deleted or hidden in search results.
So what is their stack, or where can I find more about it? A totally custom webserver? Someone commented to this effect the yesterday [1], but I couldn't find much in the way of a good writeup, except this answer from 2009 [2].
I remember hearing that they are a .NET stack with C# and SQL Server.
The only reason I know that is because I was working at a company and discussing the issues the company was running into scaling SQL Server and Stack Overflow was used as a counter example of SQL Server scalability. It lead into a long discussion of caching on high read workloads.
I'll never touch SQL Server again if I can help it.
Scott Hanselman had an interview with the Stack Overflow Director of Engineering just a few weeks ago. They cover some high-level details there [0]. As I understand it's an .NET Core monolith with a very-large (~1.5 TB RAM) SQL Server backend.
One thing about using SQL databases live in production for everything is that the architecture is amazingly simple, almost always performant, but if something goes wrong, it goes catastrophically wrong.
Amazon for new critical applications prefers NoSQL solutions for this reason since performance is flatter and not dependent on vagaries of the query optimizer.
From what I've gleaned through speaking to current and former Amazon employees you basically have to use DynamoDB for all new services.
IMHO the logical progression for applications with typical relational models is starting with an RDBMS in combination with an ORM, breaking out of the ORM when necessary for more complex/slower queries, ditching the ORM altogether when it starts to break, then evaluating sharding or moving domains into a NoSQL solution piecemeal. A well-architected monolith or series of microservices suits this paradigm which allows you to realize the productivity benefits of SQL and only worry about the deduplication, indexing, and consistency issues that come with NoSQL when it becomes actually necessary.
Then again if I were Amazon I'd probably plan for scale up front and be jaded by their experience with Oracle too.
And this is at least the 4th or 5th time within 10 days that either the website is down or performance is badly degraded.
So bad for a website that is basically the go-to resource where IT professionals get their answers.
So bad that the whole platform is closed-source, so we can't even spin multiple instances.
The main resource used by developers and sysadmins around the world is locked and centralized, and when that central place goes down all the answers go down with it.
We need crawlers and scrapers to download EVERYTHING out of the SE platforms, and they need to do so on a daily basis. All content on SE must be mirrored across the world, and if they don't want to do it then we'll do the scraping for them.
And, most of all, we need alternatives that are open and decentralized, and we need them right now.
If you use brave browser it usually is able to point you to corresponding web archive pages when SO is down. Nice to have it directly integrated into the browser
IMO it would be more interesting to not use their code and build some kind of specialized search service. One that learns to rank results from user metrics and feedback?
so like personalised google search, with the terrible results that that inevitably produces for code related content?
i am confused though. how do you think SO currently works? Both questions and answers are already ranked via user metrics (individual upvotes and historical upvotes) and feedback (comments)?
StackExchange is by no means perfect, but the copyleft content license is a key reason I feel comfortable contributing to the platform. (Which I assume is why they do it.)
> We need crawlers and scrapers to download EVERYTHING out of the SE platforms, and they need to do so on a daily basis. All content on SE must be mirrored across the world, and if they don't want to do it then we'll do the scraping for them.
I think that's already the case. Whenever I look up a technical issue, the first result is usually from SO; the next results are usually from websites that copied that first SO page
Time to take a long lunch. Hopefully it’ll be back soon, otherwise I’ll have to invent a reason to give to my boss on why I can’t get back to the office!
- Still independently owned. Imagine AWS or Microsoft buying it. Oof.
I think about LinkedIn, Github, ... the other large platforms we use for work, and SE is the only one that hasn't gone downhill.
No, I don't want them to open source the platform. No, I don't think you can do better. Yes, a few mirrors for redundancy would be excellent, but not urgent. Discoverability here would be the challenge for mirrors. They've been down less than a day total for me in 10+ years of using them.
59 comments
[ 6.3 ms ] story [ 134 ms ] thread1 https://news.ycombinator.com/item?id=32321726 2 https://stackoverflow.com/questions/676326/how-does-stackove...
The only reason I know that is because I was working at a company and discussing the issues the company was running into scaling SQL Server and Stack Overflow was used as a counter example of SQL Server scalability. It lead into a long discussion of caching on high read workloads.
I'll never touch SQL Server again if I can help it.
I'm assuming stackoverflow runs as a part of all this, and not separately.
1 https://meta.stackexchange.com/a/10370
[0] https://hanselminutes.com/847/engineering-stack-overflow-wit...
Amazon for new critical applications prefers NoSQL solutions for this reason since performance is flatter and not dependent on vagaries of the query optimizer.
IMHO the logical progression for applications with typical relational models is starting with an RDBMS in combination with an ORM, breaking out of the ORM when necessary for more complex/slower queries, ditching the ORM altogether when it starts to break, then evaluating sharding or moving domains into a NoSQL solution piecemeal. A well-architected monolith or series of microservices suits this paradigm which allows you to realize the productivity benefits of SQL and only worry about the deduplication, indexing, and consistency issues that come with NoSQL when it becomes actually necessary.
Then again if I were Amazon I'd probably plan for scale up front and be jaded by their experience with Oracle too.
So bad for a website that is basically the go-to resource where IT professionals get their answers.
So bad that the whole platform is closed-source, so we can't even spin multiple instances.
The main resource used by developers and sysadmins around the world is locked and centralized, and when that central place goes down all the answers go down with it.
We need crawlers and scrapers to download EVERYTHING out of the SE platforms, and they need to do so on a daily basis. All content on SE must be mirrored across the world, and if they don't want to do it then we'll do the scraping for them.
And, most of all, we need alternatives that are open and decentralized, and we need them right now.
https://archive.org/download/stackexchange
Awesome! Let us know when we can start using your new open source service, it must be mirrored and need it right now.
So nothing is stopping anyone to spin-up multiple instances.
not so sure about that
i am confused though. how do you think SO currently works? Both questions and answers are already ranked via user metrics (individual upvotes and historical upvotes) and feedback (comments)?
I think that's already the case. Whenever I look up a technical issue, the first result is usually from SO; the next results are usually from websites that copied that first SO page
https://www.codidact.org/
Content packages: https://wiki.kiwix.org/wiki/Content_in_all_languages
Example of how a site looks like (in this case SuperUser), hosted on my server: https://kiwix.ounapuu.ee/superuser.com_en_all_2021-04/A/inde...
And hosting it really isn't all that difficult: https://ounapuu.ee/posts/2021/12/09/self-hosting-wikipedia/
We all joke about the dependency on SO. It seems to actually be more true than perhaps we’d like to admit.
Not sure that will work.
[1] https://stackoverflow.blog/2021/09/28/become-a-better-coder-...
- FREE
- Permissive content license
- Doesn't require me to log in to read an answer
- Few / limited ads
- Data available at archive.org
- Still independently owned. Imagine AWS or Microsoft buying it. Oof.
I think about LinkedIn, Github, ... the other large platforms we use for work, and SE is the only one that hasn't gone downhill.
No, I don't want them to open source the platform. No, I don't think you can do better. Yes, a few mirrors for redundancy would be excellent, but not urgent. Discoverability here would be the challenge for mirrors. They've been down less than a day total for me in 10+ years of using them.
Owned by a VC firm, isn't it? https://www.forbes.com/sites/vijaygurbaxani/2021/06/08/the-1...
after https://vcnewsdaily.com/stack-overflow/venture-capital-fundi...
The cookie dialog being different on every site is infuriating if you’re not logged in.
it is only bad they are having some many outages these days. I am not complaining for me. but it means something is happening there
My first option was a full copy of stackoverflow. No joke.
Now, I'm reading this 5 hours letter and everything is ok, but what a wonderful site.