// Software Design · Node.jsStop Throwing new Error(). It's Lying to Your Logs.petarivanov.tech
Stop Throwing new Error(). It's Lying to Your Logs.
One distinction that sets your HTTP status, your log level, and who gets paged.
Node.js
12 articles in Node.js.
Browse by category
- // Architecture · Node.js3 Resilience Patterns That Keep a Backend Service Up When Its Dependencies Aren'tpetarivanov.tech
3 Resilience Patterns That Keep a Backend Service Up When Its Dependencies Aren't
Timeout, retry with backoff, and circuit breaker — what each one actually does, and the order to stack them.
- // Architecture · Node.jsCQRS Without the Astronaut Architecturepetarivanov.tech
CQRS Without the Astronaut Architecture
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.
- // Architecture · Node.jsHow to Stop Charging Customers Twice: A Practical Idempotency Guidepetarivanov.tech
How to Stop Charging Customers Twice: A Practical Idempotency Guide
Idempotency in plain English: HTTP, message queues, and the one detail that decides whether it's real.
- // Architecture · Node.jsVertical Slice Architecture in Node.js: One Folder Per Use Casepetarivanov.tech
Vertical Slice Architecture in Node.js: One Folder Per Use Case
Why organizing by domain module isn't enough and what to do instead.
- // Architecture · Node.jsDependency Injection in Node.js & TypeScript. The Part Nobody Teaches Youpetarivanov.tech
Dependency Injection in Node.js & TypeScript. The Part Nobody Teaches You
Learn the hidden costs about importing everything directly and the structural change you need to make.
- // Architecture · Node.jsScreaming Architecture & Colocation: Let Your Project Structure Tell the Storypetarivanov.tech
Screaming Architecture & Colocation: Let Your Project Structure Tell the Story
Learn why you should organize your code by what your app actually does, not by technical roles.
- // Architecture · Node.jsDatabase Design Doesn't Start With Table. It Starts With Consequencespetarivanov.tech
Database Design Doesn't Start With Table. It Starts With Consequences
Here's what most backend engineers get wrong about schema design and how to fix it before you hit production.
- // Architecture · Node.js2-Tier to 3-Tier Architecture: Migration Journey With Modular Monolith and GraphQLpetarivanov.tech
2-Tier to 3-Tier Architecture: Migration Journey With Modular Monolith and GraphQL
A real-world case study of migrating a two-tier architecture to a three-tier architecture.
- // Software Design · Node.jsFunctional Error Handling in Node.js With The Result Patternpetarivanov.tech
Functional Error Handling in Node.js With The Result Pattern
Learn how to improve your error handling in Node.js by using the Result Pattern.
- // Engineering · Node.jsPin your dependencies in package.json to increase your project's healthpetarivanov.tech
Pin your dependencies in package.json to increase your project's health
Avoid problems like "it works on my machine" issues and security flaws.
- // Architecture · Node.jsHow to better structure your next Node.js project? The Modular Approach.petarivanov.tech
How to better structure your next Node.js project? The Modular Approach.
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.