Nicholas Tollervey - Lessons learned with asyncio ("Look ma, I wrote a distributed hash table!")

[@WellingtonCordeiro]

3:14 is where the talk starts if anyone is wondering.

[@BayesianHorse]

I have to disagree with the opinion that asyncio is not good for multi-core systems handling tons of requests. Asyncio does support both running multiple threads and multiple processes. It also supports communication between different processes in a concurrent manner (like if one process waits for results which are computed on another process). When dealing with web applications/servers you can probably get away with just starting multiple instances of the same program (and loadbalancing).

[@ntollervey]

Andreas Klostermann OK... my answer was based upon the context of the presentation - it's an introductory talk and I wanted to focus on a simple model that wouldn't melt people's brains. As I said at the start, it's incomplete, simplified and non-exhaustive but you'll get to know enough to continue with confidence in your own self-learning about asyncio. As it happens, I *do* run up multiple instances of my DHT and you're quite correct to point out the various features you list about inter-process communication. Thanks! :-) However, in my defence, to get to a point where I could've explained how this works and why you'd want to do it would've turned the talk into a non-introductory level or caused me to have given a long, off the cuff (and therefore likely rambling and incoherent) answer. My snap decision (which I stand by) was to KISS. ;-)