Event-based system: Uklon practice [ukr]
Event-based systems are becoming more and more popular every year. At the same time, the challenges and accidental complexity we have as a result can be more complex than the problem we need to solve. Numerous architectural patterns (EDA, orchestration vs choreography, EventSourcing, etc.) can lead to unexpected traps.
Using the example of technical solutions implemented in Uklon(traffic jams, custom driver matching, driver arrival time updates), let's look at these patterns from a practical point of view.
- Solution Architect at Uklon
- 12+ years of experience in development, inc 3 in the position of Solution Architect at Uklon (the team has 120+ developers). He is responsible for the design and architecture of Uklon backend. He designs high-load distributed systems using .NET stack, Kubernetes and public clouds (AWS, GCP).
- Alexander’s areas of interest are designing distributed systems, event-driven architecture (EDA), DDD, event sourcing, CQRS, actor model, data-intensive applications.
- Linkedin, Facebook