📝[Docs]: Blog about how netflix handle 200M events per day

[Adez017]

Is there an existing issue for this?

• I have searched the existing issues

Issue Description

A comprehensive blog on strong hold on data part with clear explanation of how netflix architecture or data pipelines handles and process 200M events per days.

Suggested Change

Nuil

Rationale

No response

Urgency

High

Record

• I have read the Contributing Guidelines
• I want to work on this issue

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[sanjay-kv]

Maybe some relevant backlinks and attaching random youtube embed also helps here.

• 1,800 – 2,500 Long-form ranks 3× better for technical topics
• Intro: The scale problem
• introduce what is event with your dashboard screen shot
• then The architecture — Kafka, Flink, Keystone (~500 words) ⭐ Core
• 5 lessons for your own data pipeline (~300 words)
• Connect the tech to real UX - more ss better. the real dashboard add value

[github-actions]

👤 Issue assigned to @Adez017.