The Evolution of a Multifaceted Node.js Project Architecture
summary
Koyfin’s Node.js backend evolved from an MVP into a complex system of dozens of microservices handling large volumes of financial data and thousands of heterogeneous messages per minute. The talk describes the operational problems that arose—managing many repositories, ensuring consistency, throughput and fault tolerance while retaining flexibility—and presents the tools and techniques the team tried and the solutions they adopted to address those challenges.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 4:07MVP problems in startups
- 7:07Monolith to microservices
- 10:15Service responsibility
- 13:12Microservice communication
- 14:17Integration contracts
- 15:43TypeScript first steps
- 18:34TypeScript advantages
- 23:06Third-party data validation
- 27:27Gradual TypeScript migration
- 30:41Technical debt management
- 31:03Big data computation
- 36:30Caching for performance
- 39:39Cache trade-offs
- 43:54Architecture recommendations
- 47:25Technical debt myths
- 48:08Q&A
related talks
24mMicrofrontends
46mArchitecture of a Modern Enterprise Node js Application
43mPatterns for Reactive node.js Microservices
40mDeploying node.js at scale
31mKeynote Panel: Node.js at Massive Scale
29mNode.js Micro-Services
30mThe working Architecture of Node.js Applications
01h 00m10 years of microservices at FINN.no - and we still haven’t slain that dragon!