News for hackers. Stuff that matters.
Re:Learn how to design large-scale systems by mabbo on Friday July 13, 2018 @11:47AM (#17523927)
This design, roughly, is being used very widely and is well-documented everywhere. But does anyone know of any lesser-known yet equally functional designs that work at the same scale?

Are there cases this design does not work for?

Re:Learn how to design large-scale systems by bsenftner on Friday July 13, 2018 @01:29PM (#17524912)
Yes. One can use a C++ library like Restbed and embed the web server directly into a compiled executable that uses SQLite as an embedded database. The "large-scale, multi-system architecture" in such common use today is completely unnecessary when faced with this setup. I have multiple Restbed integrated applications whose entire disk footprint is 7MB; they can run on a $99 Intel Compute Stick, perform industrial grade facial recognition with multiple HD video streams, and still overwhelm traditional web stacks with events and data when pertinent events the software needs to report start emitting over the wire.

The "only catches" are the developer(s) need experience working in multi-threaded C++, and they need to understand the traditional web stack they are eliminating.

Re:Learn how to design large-scale systems by s_ngularity on Friday July 13, 2018 @07:06PM (#17527613)
What about fault-tolerance though? That's definitely a single point of failure scenario.
Re:Learn how to design large-scale systems by bsenftner on Monday July 16, 2018 @06:51PM (#17545850)
Run as many instances as your fault tollerance requirements needs. The expense of adding another physical box is trivial when that physically box is $99 to $250 total to own. They "pay for themselves" in their first month of use, versus any cloud configuration running any 'amp or node or Mean or simply "traditional" web stack.