What’s new in Cloud Firestore at Google I/O 2023

Поделиться
HTML-код
  • Опубликовано: 9 май 2023
  • Developers love Firestore because of how quickly and cost-effectively they can create an application end-to-end. Over 4 million databases have been created in Firestore, and Firestore with Firebase Authentication powers more than 1 billion monthly active users. In this session, learn what’s new from Firestore including: the latest query features, Eventarc integration that supports triggering in new compute destinations, and Terraform provisioning.
    Resources:
    Cloud Firestore → goo.gle/3KiLGz0
    Speaker: Dong Chang
    Watch more:
    Watch all Firebase Sessions → goo.gle/IO23_firebase
    Watch all the Technical Sessions from Google I/O 2023 → goo.gle/IO23_sessions
    Watch more Mobile Sessions → goo.gle/IO23_mobile
    Watch more Web Sessions → goo.gle/IO23_web
    Watch more Cloud Sessions → goo.gle/IO23_cloud
    All Google I/O 2023 Sessions → goo.gle/IO23_all
    Subscribe to Firebase → goo.gle/Firebase
    #GoogleIO
  • НаукаНаука

Комментарии • 8

  • @Firebase
    @Firebase  Год назад +6

    Watch all the Firebase Sessions → goo.gle/IO23_firebaseyt_pin

  • @jialx
    @jialx Год назад +4

    And just casually the ‘in’ condition is three times better niceeee

  • @pauldewit8088
    @pauldewit8088 Год назад +5

    Did I just hear multiple databases per project?? When will this be available? I have been dying for this feature!

    • @Bazinga2u2
      @Bazinga2u2 Год назад

      Finally 🎉
      A long awaited feature, wish they could focus on it a bit more tho

    • @MysticZA
      @MysticZA 11 месяцев назад

      Does this mean multi-tenancy solutions!? Or at least multi-division solutions within a client?
      Pumped 🔥

  • @John-qt6qk
    @John-qt6qk 9 месяцев назад

    Awesome

  • @user-es2jx6ir9s
    @user-es2jx6ir9s Год назад +2

    For the love of god allow us to edit document and collection names!

    • @shubhamtariyal3465
      @shubhamtariyal3465 Год назад

      how will it be useful? Most of the time users are unaware of these ids so we can bypass this issue by some means not requiring to updating names.