Hacker News new | past | comments | ask | show | jobs | submit login

While I largely agree with the thesis of this article, I actually really like the entire "scalable microservice" way of designing things.

It's overkill for anything I need to do, but my home server is six 8-core ODroid devices, orchestrated with Docker Swarm, with most of my services on there being load-balanced, and glued together with Kafka if they need to talk to each other.

Do I need my internal video streaming server to be able to scale horizontally? Of course I don't, there's only ever three people max watching things from there at any point in time. However, I find that, overall, my brain thinks more-or-less in terms of these microservices, and it doesn't really hurt much to do it that way.

If I find it pleasant enough to do, why the hell not make it hyper-scalable and able to reach Google levels?

EDIT: Just a note, I know that Docker Swarm probably isn't quite capable of Google-size. Still, moving to Kubernetes or something wouldn't be terribly hard (the reason I didn't use it was because a few years ago I had some issues with Kubernetes on ARM and Swarm worked outta the box).




There are Swarm clusters in production with tens of thousands of hosts. There's nothing in Swarm that makes that impossible.


Fair enough; I didn’t know that Swarm was used for any large projects because apparently I don’t know how to read or use search engines; I stand corrected!

I guess that backs up my original point even more then; my stupid video streaming server might actually be able to scale to Google size some day :)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: