Re:Comparing a web service written in Python and Go [pdf]
by Consultant32452 on Monday October 19, 2015 @11:22AM
(#10413449)
Let's say you have a REST request come in. In order to fulfill that request you need to make 10 REST requests of your own to various back-end systems. If you can make some of those requests asynchronously you'll greatly reduce your response time. While I suppose you could mangle your way through it multi-process, it seems like a bastardization of the model.
[ Parent
| on HN ]
Re:Comparing a web service written in Python and Go [pdf]
by falcolas on Monday October 19, 2015 @01:20PM
(#10414273)
If you're just sending HTTP requests, regular threading in Python works fine - waiting for a socket response doesn't block the execution of other threads.
Python threads are real threads, and things like blocking socket IO does not block Python execution in other threads.
Re:Comparing a web service written in Python and Go [pdf]
by dec0dedab0de on Monday October 19, 2015 @11:50AM
(#10413646)
While I suppose you could mangle your way through it multi-process, it seems like a bastardization of the model.
That kind of sounds like you're nitpicking over an implementation detail. Which brings me back to my original confusion. If I have an interface that allows me to articulate concurrent tasks, I don't see the difference between threads, processes, or separate machines.
Again, this is assuming we're not in a resource constrained environment, and we're not doing something so processor heavy that it really should be compiled.