How does Uber scale to millions of concurrent requests?

Поділитися
Вставка
  • Опубліковано 28 вер 2024

КОМЕНТАРІ • 57

  • @Echoes2165
    @Echoes2165 2 роки тому +93

    Demo of the new text to speech seems impressive!

  • @sunilkatti7197
    @sunilkatti7197 2 роки тому +1

    Loved the fact that they were tackling with the exact same problems like we do day to day… saga pattern, eventual consistency.. and also stumbling upon similar solutions. So relatable and glad they chose spanner. Next logical step is to pipeline that data into BQ and run your ML models 😊

  • @SubtleAsh-TheImmortal
    @SubtleAsh-TheImmortal 2 роки тому +19

    I love the host’s exuberance, great video!

    • @pvergadia
      @pvergadia 2 роки тому +2

      Thank you very much 🙂

  • @ginnybalbo
    @ginnybalbo Рік тому +2

    Love this video, especially hearing the reality of maintaining operations through the continuous improvement and rollout processes. I am very curious about the Geospatial Index and the matching engine components.

  • @harishdurga
    @harishdurga 2 роки тому +1

    honestly, just the concept of being able to handle millions of traffic is so exciting...but at the same time with all the networking and distributed architecture involved it's so complex to understand it. I was able to grasp only 30 - 35 percentage of it. I wonder about the Spanner's USPs compared to AWS Aurora

  • @Xy9d
    @Xy9d 2 роки тому +32

    I love these use cases. They are great in many ways. We can gain an understanding of how a system as big as uber works, understand its challenges and and understand how different Google Cloud Platform technologies can help on this. I vote for more videos like this. o/

  • @vineettalashi
    @vineettalashi Рік тому

    Demo of the new text to speech seems impressive! Good work Google

  • @abhishekdanej
    @abhishekdanej 2 роки тому +2

    Amazing . This is truly planet scale!

  • @thalaajith8302
    @thalaajith8302 2 роки тому +4

    is he reading ppt presentation?

  • @ravikanth6178
    @ravikanth6178 2 роки тому +1

    An interesting topic on spanner

  • @datasqlai
    @datasqlai Рік тому

    How the new google cloud Alloy db different from Cloud spanner ? Now google have 3 different relational DB's- Cloud SQL, Cloud spanner and Alloy DB. What is the intent behind all these DB's ?

  • @techit_ezy
    @techit_ezy 2 роки тому +1

    Can I get the PPT from where the engineers are reading this.

  • @maverickmaverick5
    @maverickmaverick5 2 роки тому

    Uber could have done a better job at explaining business needs to Uber Request flow and what/why inconsistencies were created that required fixing with Saga or why serialization is needed.

  • @evanskipyegon4764
    @evanskipyegon4764 2 роки тому +1

    Is there any use case in Africa companies

  • @baranidharanpn
    @baranidharanpn 2 роки тому

    Does Uber has any third party agents who can charge only 50 - 60% of original fee from customers and book orders on their behalf… any thoughts here pls ?

  • @MykelOkuboyejo
    @MykelOkuboyejo 2 роки тому

    Really great questions!

  • @jafarshaik5160
    @jafarshaik5160 2 роки тому +4

    Wow 😳

  • @Tamil-Murugan
    @Tamil-Murugan Рік тому

    I really like the part "...You literally changing the car tyres when the car is moving..." 🙂

  • @chakrabortyraj
    @chakrabortyraj 2 роки тому +1

    Uber is amazon . aren't they using AWS?
    why google is excited for Uber's/ AWS's success story?

    • @chandrakanthotkar7262
      @chandrakanthotkar7262 2 роки тому +2

      For transactional Database they are using Spanner, One of the best Hybrid Cloud User Story

  • @jugsma6676
    @jugsma6676 2 роки тому +9

    The team have been doing absolutely amazing to keep the service running with no downtime. And really amazed to know Uber using all these tools during migration.

  • @MrManjax
    @MrManjax 2 роки тому +6

    It's totally incredible how some of the scaling considerations were handled and seamlessly migrated between the two underlying architectures. Kudos to the teams that enabled this!!

  • @Filip-ci3ng
    @Filip-ci3ng 2 роки тому +6

    Uber succeeded by ditching responsibility for drivers and consumers. Taxi drivers and passengers in old business model had employee insurance, companies cared about workers and clients. Uber makes billions while not providing any of that. Everyone loses

  • @itbrains_itbrains
    @itbrains_itbrains 2 роки тому +3

    Loved the use case. Need more videos like this

  • @dev-luisbenavidesandrade
    @dev-luisbenavidesandrade 2 роки тому +2

    awesome use case! love it :)

  • @robertogiardi3475
    @robertogiardi3475 2 роки тому +2

    In terms of human resources, how many people have worked to achieve these results? Thank you

  • @vasavikotha5619
    @vasavikotha5619 2 роки тому +3

    Great explanation!!

  • @bhanumar
    @bhanumar 2 роки тому

    fact that spanner gives ACID guarantees on planet scale is testament to pros that build this tech

  • @defamationlaw
    @defamationlaw 2 роки тому

    Interesting watching this as an ex Enterprise Architect and now a Lawyer! Good to see these new solution architectures.

  • @coolcalmcomposed
    @coolcalmcomposed 2 роки тому

    Very useful and nicely explained video.Can you do a video on any Social media like Facebook , Instagram using GCP products.

  • @gibson3730
    @gibson3730 2 роки тому

    Great use case introduction !

  • @ErwinSaavedra
    @ErwinSaavedra 2 роки тому

    it did!!! thank you for this!

  • @shasha6538
    @shasha6538 2 роки тому

    one of the best videos in youtube right now.

  • @clinton11994
    @clinton11994 2 роки тому

    When we say moving the completed orders to new system powered by spanner and new orders will also be handled by new system powered by spanner, how do we handle auto increment keys conflict ? ( Just asking if in case we have auto increment keys ), one work around is to have a gap of a estimated numbers in New database i.e. say old db current order no is 1000 in New db we start with 2000 so that when this db is up and old data from previous db is copied over there will be no key conflict.

    • @TBasianeyes
      @TBasianeyes 2 роки тому +3

      You avoid that by not using auto increment keys, you use randomized UUIDs for primary keys. They already came from distributed nosql so that didn't change.

  • @neerajkumarsingh
    @neerajkumarsingh 2 роки тому +2

    amazing , got goose bumps while watching. well done to Ankit. , Preetam, and Priyanka and team.

  • @kchahal7152
    @kchahal7152 2 роки тому

    Just an observation, Indians are present everywhere on the top(IT, Pharma, Scientists, Banks, Industrialists etc) in the middle and in bottom as well, what happens if all NRI comes in India and focus on building and using their expertise in making India great. Would love to hear your opinions, suggestions or consequences.