Scaling Push Messaging for Millions of Devices @Netflix

InfoQ Dev Summit Boston, a two-day conference of actionable advice from senior software developers hosted by InfoQ, will take place on June 24-25, 2024 Boston, Massachusetts.

Deep-dive into 20+ talks from senior software developers over 2 days with parallel breakout sessions. Clarify your immediate dev priorities and get practical advice to make development decisions easier and less risky.

--------------------------------------------------------------------------------------------------------------------------------------

Susheel Aroskar talks about Zuul Push, a scalable push notification service that handles millions of "always-on" persistent connections from all the Netflix apps running. He covers the design of the Zuul Push server and reviews the design details of the back-end message routing infrastructure that lets any Netflix microservice push notifications to any connected client.

#SoftwareArchitecture #Netflix #ZuulPush #InfoQ #QConNewYork

[prudvim]

Much better than watching "Design a Notification Service" System design interview videos.

[zkwentz]

The “ask client to close” due to TCP wait avoidance, is brilliant. Well done!

[audi]

This talk is so good. Especially the mention of benchmarking numbers.
m4.large ~ 8G, 2vCPU = 84000 concurrent connections. ❤️

[bedtimestoriesforkids]

I am watching this right before a system design session! :)

[namansharma]

Great work to figure out asking the client to drop the connections and also scale on connections per seconds.

[at_tap]

Extremely well conducted video, very informative and explained without any wrinkles. Kudos!!

[jmitesh]

nit pick here, but how does sharding for availability help in push registry feature checklist? Its because it protects by only some portion of connection server goes down?

[km_]

Really neat presentation with much informative content.

[RanjithVj]

Excellent presentation. Thanks for getting into implementation details!

[huhu]

Amazing talks! I learn a lot from this video. "Ask client to close" is really brilliant. Randomized the connection time is also very impressive. I have seen random backoff algorithm, don't know it can also be used in this scenario.

[BHARATKUMAR-leeq]

I think some confusion at ELB. ELB operates at Layer 4 which means at the TCP layer already.

[unmeshchougule]

Question : when you say client opens connection and stays connected to that server, wouldn't it talk to load balancer and not the actual server here? So even if you deploy new server behind that load balancer there won't be any issue of the connection closing and re-opening as you mentioned?
Please shed some light if I am missing something here.

[lalanashree]

One of the best 'Notification Design videos' seen so far.

[ThanosVassilakis]

This a great talk that really warms up after 20 minutesin when the talk goes into operation details.

[PankajKumar-vitn]

Very good talk. I also liked some of the questions in the end.

[attention_shopping]

what a great talk. so dense, no fluff

[Nemosaur]

This has been so insightful
Thank you so much for this talk!

[pothiq]

It's truly comprehensive. Thanks for the nice presentation in a very understandable way.

[pragmaticsoftwareengineer]

Brilliant Talk.. Learned so much.. Thanks Susheel.

[AbhijeetJadhav]

Super comprehensive and very inspirational! Thank you.