Scaling Uber's Real-time Market Platform
•
4 recomendaciones•1,382 vistas
Matt Ranney explains the Uber architecture overall, with a focus on the dispatch systems, the geospatial index, handling failure, and dealing with the distributed traveling salesman problem.
Recomendados
Recomendados
Más contenido relacionado
Similar a Scaling Uber's Real-time Market Platform
Similar a Scaling Uber's Real-time Market Platform (20)
Más de Trieu Nguyen
Más de Trieu Nguyen (20)
Último
Último (20)
Scaling Uber's Real-time Market Platform
- 15. partners riders dispatch post trip processing money maps / ETA services databases
- 16. partners riders dispatch post trip processing money maps / ETA services databases
- 17. partners riders dispatch post trip processing money maps / ETA services databases
- 18. partners riders dispatch post trip processing money maps / ETA services databases
- 19. partners riders dispatch post trip processing money maps / ETA services databases
- 20. MICROSERVICES
- 21. partners riders dispatch post trip processing money maps / ETA services databases
- 22. partners riders dispatch post trip processing money maps / ETA services databases
- 23. partners riders dispatch post trip processing money maps / ETA services databases
- 24. partners riders dispatch post trip processing money maps / ETA services databases
- 25. dispatch post trip processing money maps / ETA services databases
- 27. •1 rider, 1 vehicle •Moving people •Sharding by city •MPOF PROBLEMS
- 28. dispatch post trip processing money maps / ETA services databases
- 33. supply humans demand humans demandsupply Dispatch DISCO geo by supply geo by demandrouting / ETA
- 34. supply humans demand humans demandsupply Dispatch DISCO geo by supply geo by demandrouting / ETA
- 35. demandsupply Dispatch DISCO geo by supply geo by demandrouting / ETA
- 36. Source: Geometry on the Sphere: Google's S2 Library
- 37. Source: Geometry on the Sphere: Google's S2 Library
- 42. •reduce waiting •reduce extra driving •lowest overall ETAs GOALS
- 43. D1 Pickup request S1 best ETA +8 mins time S1 pickup after 8 mins
- 44. time S2 drop off +2 mins S2 ETA from drop off +1 min D1 Pickup request S1 best ETA +8 mins S1 pickup after 8 mins
- 45. time D1 Pickup request S2 best ETA +3 mins S2 pickup after 3 mins
- 46. time S2 pickup D2 D1 Pickup request S2 best ETA +3 mins D2 Pickup request S2 best ETA +1 mins S2 pickup D1 S2 drop off D1 S2 drop off D2
- 47. demandsupply Dispatch DISCO geo by supply geo by demandrouting / ETA
- 52. •performance •forwarding •language support •proper pipelining •checksums / tracing •encapsulation GOALS
- 54. AVAILABILITY •everything retryable •everything killable •crash only •small pieces
- 55. CULTURAL CHANGES •no pairs •kill everything •even databases
- 56. load balancerservice A service B
- 60. •overall latency ≥ latency of slowest component •1ms avg, 1000ms p99 •use 1: 1% at least 1000ms •use 100: 63% at least 1000ms •1.0 - 0.99^100 = 0.634 = 63.4% LATENCY
- 61. service A service B (1) service B (2) req 1, also B (2) +5ms req 1, also B (1) cancel req 1
- 63. partner app dispatch DC1 Location Updates State Digest dispatch DC2 Location Updates State Request
- 64. THANKS