I’m the writer of this. I linked to this presentation very clearly throughout the article as a source.
This was an article meant to resurface learnings from something that happened a decade ago, with added images and a clear distillation so that somebody doesn’t have to watch the 45 minute presentation to understand what happened.
I’m sorry you didn’t like it.
But I hope you can see the value I’m trying to provide here, as someone myself who doesn’t really have the time to sit through hour-long presentations to learn something.
I think most people here see the value of the article. Thank you for publishing it.
Parent comment was also valuable to me, for seeing how important it is to listen to others before jumping to conclusions about the worthiness of something.
There was a time when many of the OGs here would write original content, not for subscribers, not to make money, but to share our ideas, facilitate our own learning, to have to defend our ideas, to go deeper, learn more, and get better at our art. That was the way, once.
I'm on my nth account. 12,13 submissions year and barely a few this year isn't going to feed the masses. Produce more or accept that others will submit articles not up to your standards.
I got great value out of the article and shared it with my colleagues. Were it not for your effort, we'd never stumble upon this info, even though it existed in some other form.
Uh, I really liked both the article and the posts in this thread. Both are timely and right on target for me as I work to get my Web site running on the Internet.
I like the 11 million unique users a month early in the company -- simple architecture, popular programming tools and languages, small team, and likely enough ad revenue to pay the bills and get some earnings!
I wrote my code using Microsoft's Visual Basic .NET, ASP.NET, SQL Server, and one use of platform invoke. The code appears to run as intended.
I like the mention of DB (relational data base): I wrote the code using a free version of Microsoft's SQL Server. Right, it's only for development work, has some severe limits on DB size, gets expensive for a production version, also a pain since have to count processor cores, was glad to see Postgres and MySQL since have been planning to use one of those. I liked seeing the mention, and remark on power, of key-value stores (e.g., Redis) since I wrote my own key-value store, with all the data just in main memory, using two instances of the .NET collection class.
Now with TB (trillion byte) main memories am even toying with the outlandish idea of keeping nearly all the DB data in main memory with SQLite -- outlandish!
And, liked seeing the steps up in capacity. That there are likely better architectural ideas now doesn't disappoint me!
The outlines of the architectures of even huge Web server farms was really good to see. You mean Google, Facebook, Amazon, Microsoft, etc. have surprisingly simple architectures???
WOW.
I didn’t “slap” any date on top of the article. 2 Oct 2023 is the date I published my article. (This is how blogs on the Internet work.)
The first line of the article says that this all happened in 2012. I’m not sure I could get any clearer there.
The “GPT distillation” phrase is pretty rude. Anyone reading the article can see the difference between it and the presentation. Every “hand-drawn” image in the article is created by me in Excalidraw, and any images from the presentation are sourced with a very clear link to the presentation.
If you have any constructive feedback, I am happy to listen and take it into account.
Otherwise, I’m not really a fan of the rudeness. Thanks.
Don't worry about it man. Some people just like to complain. Don't take it to heart.
I found it interesting and valuable. It doesn't matter if the base content originated from another source. I would never have seen that original content. I saw this. It's ok.
I missed the original InfoQ presentation so this post was definitely useful to me. In particular I'm working on something related to the clustering vs simple sharding dilemma so finding another big name use case is quite helpful. Thanks and don't let the haters get you down.
We really need to ban attitudes like yours. Stop hn from going the way stackoverflow went. Because a question has been asked before and you know the answer doesnt mean it cant be asked and answered again in many different forms so to speak.
It is just repackaged content from the original Pinterest presentation back in 2012:
https://www.infoq.com/presentations/Pinterest/