Re:Why scaling and parallelism remain hard even with new too...
by Jtsummers on Wednesday August 10, 2016 @03:00PM
(#12264035)
This depends on your definition of scaling.
You're creating (relatively) heavyweight servers to handle multiple instances and hiding them behind a reverse proxy.
And this is for a very specific use-case. Not everything is HTTP, and not everything HTTP is handled (well) by a LAMP stack.
Certainly, as pcwalton points out, a LAMP stack will not handle scalability of your graphics (while hitting desired performance characteristics, at least). A LAMP stack is unlikely to be appropriate to the sort of scaling that map-reduce can perform. A LAMP stack won't handle, in the case of my office, handling an arbitrary number of connecting radios.
===EDIT===
> Threading is hard and I'm sure will always be hard. But threading is the wrong way to scale or parallelise.
Threading is an implementation of concurrency/parallelism. Spawning multiple servers behind a reverse proxy, like you seem to be suggesting, is one method for handling scaling issues.
But the models used to make effective use of threaded concurrency (actor model, CSP, even shared memory done well), also work in designing larger systems that need to scale beyond a single computer/CPU.
You're creating (relatively) heavyweight servers to handle multiple instances and hiding them behind a reverse proxy.
And this is for a very specific use-case. Not everything is HTTP, and not everything HTTP is handled (well) by a LAMP stack.
Certainly, as pcwalton points out, a LAMP stack will not handle scalability of your graphics (while hitting desired performance characteristics, at least). A LAMP stack is unlikely to be appropriate to the sort of scaling that map-reduce can perform. A LAMP stack won't handle, in the case of my office, handling an arbitrary number of connecting radios.
> Threading is hard and I'm sure will always be hard. But threading is the wrong way to scale or parallelise.Threading is an implementation of concurrency/parallelism. Spawning multiple servers behind a reverse proxy, like you seem to be suggesting, is one method for handling scaling issues.
But the models used to make effective use of threaded concurrency (actor model, CSP, even shared memory done well), also work in designing larger systems that need to scale beyond a single computer/CPU.