News for hackers. Stuff that matters.
Re:Microservices by seibelj on Thursday September 15, 2016 @03:13PM (#12508936)
I swear, the HN front page algorithm is easily gamed, this gets a few points quickly and it rises straight to the front page. I don't know if HN is accounting for vote rings but some penalizing should be implemented.
Re:Microservices by teen on Thursday September 15, 2016 @03:28PM (#12509062)
agreed, most of the points this article makes are invalid as well. google has been running the microservices pattern forever and seems to scale fine. for example he mentions that costs are ndoe based but no where in a microservice pattern does it say each service has to run on its on vm
Re:Microservices by cbernini on Thursday September 15, 2016 @03:49PM (#12509240)
AFAIK the content is curated. So content with a little ammount of upvotes can show up if some admin wants to.
Re:Microservices by striking on Thursday September 15, 2016 @04:31PM (#12509577)
It's not curated. People used to be asked to repost their content if the admins thought it was interesting, but this no longer occurs. (This turned into a system that could automatically repost content considered interesting; I've stopped posting stories as often, so I'm not sure if it still happens.)

Furthermore, there are protections against vote rings. If, for example, someone votes directly on the URL for a story, or if the referrer is often the same, those votes are discarded.

However, you're right that the algorithm has evolved over time. Visit https://news.ycombinator.com/classic to see the previous algorithm in action.

Re:Microservices by cbernini on Thursday September 15, 2016 @04:37PM (#12509614)
I remember some people complaining about it some time ago, thanks for pointing that out then. :D