Stateful app as an efficient way to build dispatching for riders and drivers [ukr]
Within the Uklon service product line, we consistently employ a widely accepted and easily understandable programming paradigm — the stateless approach. However, there exist various business scenarios where this approach may fall short when it comes to resource utilization, efficiency, and ongoing maintenance. Furthermore, its predictability in handling peak loads can also be questioned.
In this presentation, we will explore the following key areas:
- Scenarios where the stateless approach demonstrates suboptimal performance;
- Scaling stateful services through effective partitioning and replication strategies;
- Developing strategies for comprehensive disaster recovery, including Recovery Time Objective and Recovery Point Objective;
- The evolutionary path from actor-based architectures to the more inherent classic stateful architecture.
- Solution Architect at Uklon
- 13+ years of experience in development, inc 4 in the position of Solution Architect at Uklon (the team has 220+ 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