10 articles on Node.js.
Browse by tag
You don't need event sourcing or a second database. Just split reads from writes, and finally fix the 20-method service nobody wants to open.
Idempotency in plain English: HTTP, message queues, and the one detail that decides whether it's real.
Why organizing by domain module isn't enough and what to do instead.
Learn the hidden costs about importing everything directly and the structural change you need to make.
Learn why you should organize your code by what your app actually does, not by technical roles.
Here's what most backend engineers get wrong about schema design and how to fix it before you hit production.
A real-world case study of migrating a two-tier architecture to a three-tier architecture.
Learn how to improve your error handling in Node.js by using the Result Pattern.
Avoid problems like "it works on my machine" issues and security flaws.
In this article, I will share my opinion on how to structure your next Node.js project. In the past, I’ve worked on various projects both with Node.js and other technologies. A well-structured project is crucial for the developer experience (DE), scalability and maintainability of the application, testing, and much more.