How business requirements shape architecture: evolution of the notification service at Lamoda Tech
summary
The talk describes how Lamoda Tech’s notification service architecture evolved in response to concrete business requirements, showing which requirements (like scalability, delivery guarantees, or integration needs) drove specific technical choices. It explains the architect’s approach to translating business needs into engineering decisions and the resulting technologies and design patterns used in the notification system.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:51Product requirements
- 8:36Event pipeline design
- 16:42Implementation and issues
- 22:02Optimization and scaling
- 25:56Feature expansion
- 31:13Architecture lessons
- 33:21Conclusion
- 34:23Q&A
related talks
41mChallenges and solutions: evolution of the technology architecture
50mMicroservice specifics illustrated by an e‑commerce platform
55mDevOps as Architecture in Process: Two Systems for Engineering and Business
36mApplication Architecture Patterns
01h 00mDescribing and Documenting Your Architecture
54mArchitecture Is Not Nonsense
45mKeeping Up with the Times: Flexible Architectures
50mA Practical Use Case of Software Architecture Evolution