I/O

Showing 1-2 of 2 results
EngineeringIcon ChevronTechnology

Server-side I/O Performance: Node vs. PHP vs. Java vs. Go

by Brad Peabody

Understanding the Input/Output (I/O) model of your application can mean the difference between an application that deals with the load it is subjected to, and one that crumples in the face of real-world uses cases. Perhaps while your application is small and does not serve high loads, it may matter far less. But as your application’s traffic load increases, working with the wrong I/O model can get you into a world of hurt.

16 minute readContinue Reading
EngineeringIcon ChevronTechnology

Why The Hell Would I Use Node.js? A Case-by-Case Tutorial

by Tomislav Capan

Node.js shines in real-time web applications employing push technology over websockets. What is so revolutionary about that? Well, after over 20 years of stateless-web based on the stateless request-response paradigm, we finally have web applications with real-time, two-way connections, where both the client and server can initiate communication, allowing them to exchange data freely. This is in stark contrast to the typical web response paradigm, where the client always initiates communication. Additionally, it’s all based on the open web stack (HTML, CSS and JS) running over the standard port 80.

14 minute readContinue Reading

Join the Toptal® community.