The working Architecture of Node.js Applications
summary
A production-proven volcanic architecture runs across Node.js PHP and Perl for eight years and organizes logic into a coarse-grained domain model and per-use-case service classes so one endpoint one class maps to a single service with a run method, declarative validation, and async/await error handling. Controllers remain thin glue, GraphQL and REST reuse the same services, responses use whitelisted dumps — never return domain objects — and a starter kit is planned for open source release.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:32Monolith or Microservices by default?
- 2:45What is the most popular architecture today?
- 3:21Microservices: Big and distributed ball of mud
- 5:14What is the best architectural decision?
- 7:20So, we start with monolith in 90% of cases
- 8:56What is Monolith?
- 9:57Which web-framework to choose?
- 10:14Your application architecture should not depend on a web framework
- 10:37We use MVC why do we need another architecture?
- 11:57Is Model (MVC) and Domain Model the same?
- 17:07How do we cook the service layer?
- 18:55NodeJs example of a Service class
- 24:06GraphQL support
- 25:13Full example: User registration
related talks
46mArchitecture of a Modern Enterprise Node js Application
35mRethinking Enterprise Architectures with Node.js
47mCreating Enterprise Web Applications with Node.js
24mWhy Node.js Needs an Application Server
41mArchitecture in Node.js using NestJS
39mThe Structure of Node.JS Applications
53mHexagonal Architecture in a Nodejs Project
02h 44mHexagonal Architecturoplasty of a Node.js Backend