Multiple threads or only one thread, and why should it matter? Blocking or non-blocking IO, and what benefits do each of them offer? What’s the problem of using callbacks? Hold on to your hats, folks – in this episode, Esko, Andy and Otto plow through some of the most fundamental questions regarding runtime environments. 

Guests

Andy Davies is a software developer who likes making other developers’ lives easier, usually by providing libraries, tooling, infrastructure, build systems, and ways of working. He likes keeping things simple. He doesn't like Kubernetes.

Otto Paaso also likes simple things (and static types). For the past 12 years he has been working on embedded, desktop and web products, as well as the necessary backend and infrastructure technologies to make things rock. 

Host

Esko Lahti is an engineer who wants to know how things work under the hood, no matter how many threads are involved. He has no horse in the Node.js vs JVM race.

Episode links

• V8 JavaScript Engine: https://v8.dev/
• The Node.js Event Loop: https://nodejs.dev/learn/the-nodejs-event-loop
• A Guide to CompletableFutures in Java: https://www.baeldung.com/java-completablefuture
• Overview of blocking and non-blocking IO: https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/
• Asynchronous programming in C#: https://docs.microsoft.com/en-us/dotnet/csharp/async

About Reaktor

Fork Pull Merge Push is a podcast by Reaktor, a strategy, design and technology company changing how the world works. Reaktor has offices in New York, Amsterdam, Stockholm, Tokyo, Helsinki, Turku and Tampere.

Reaktor is always on the lookout for bright software developers to work in health, security, emerging technologies, and much more. See www.reaktor.com/careers.

@ReaktorNow
#FPMPod

Episode source