Push Notifications in RuStore: How We Built Our Own Transport to Replace Google Firebase

on YouTube ↗53m

" summary

Describes an in-house push-notification transport built for RuStore as an alternative to Google Firebase, focusing on an architecture that delivers mobile pushes with minimal latency. Covers reliability and horizontal scalability using Redis Cluster and Scylla, and defenses against DDoS on the public API.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 2:59Why build our own push
3. 7:38How RuStore Push works
4. 14:32Service architecture
5. 21:56Push notification process
6. 29:42Operations and scalability
7. 35:45Mail.ru integration
8. 40:04Results and plans

" related talks

• 01h 15mFirebase Is More Than Just PUSH MessagesAndrey Nemtsev · Mobius 2020 Piter
• 27mNetworking & Persistence in Mobile Applications at ScaleJake Schwartz · 360iDev 2017
• 46mRethinking SyncingJoe Keeley · AltConf 2019
• 50mBuilding a Serverless API With Google, Firebase and PostgreSQLRob Conery · NDC Oslo 2017
• 47mLaunching Beeline with Firebase Realtime Database, Authentication and FunctionsChetan Padia · Mobile Era 2017
• 32mPeristence as the Single Source of TruthSaket Narayan · droidcon Berlin 2018
• 36mBuild a Cloud Native Asynchronous Messaging System For Scale With RedisMadelyn Olson · KubeCon + CloudNativeCon North America 2022
• 07mAuto alerts for Firebase users with Functions, Logging, and BigQueryJaisen Mathai · Google I/O 2022