How Tinder / Bumble does Matchmaking? System Design Charcha with
Vložit
- čas přidán 23. 03. 2024
- Many more such specific problems discussed in the series here - • System Design Charcha
Checkout details and enroll for our LIVE courses here-
www.educosys.com
If you appreciate the hard work or want to be consistent with the bootcamp, Please 𝐬𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 here - / @keertipurswani
You can also connect with me on-
LinkedIn - / keertipurswani
Instagram - (for personal, raw and real side of my life) - keerti.purs...
#systemdesign #hld #softwaredeveloper #softwareengineer
Appriciate you Keerti maam for making such informative content love from Bangalore, I do share your videos in our groups
Thank you soo much broo for sharing ❤❤
Really amazing series. We want such rare discussions!!!
Not sure about Cassandra, I feel when we have a very complex search query structure like - filter on age, location, interests, gender, hobbies etc a search engine that supports text based search (basically quick indexing on props) like ES may be an option. But Cassandra looks like a horrible choice for a read-heavy system like Tinder :(
Surprised to see Gaurav was okay with this lol
I have been loving programming. And should me go to this channel. But now I love you ❤.
I'd strongly recommend discussing less about the rationale behind certain requirements like why the active filter is important and more about the infrastructure design.
Completely agree with you. This video seems more of LLD than HLD. They did not discuss about many things which are required in a HLD.
he is really great..! Thanks for sharing this video
22:50 regarding the choice of using C*, yes it compresses the data (column wise). But, match making is read heavy operation. So, C* vs SQL, there is nothing great that C offers. The biggest advantage is horizontal scaling when it comes to storing data.
If you store entire Country data in a single Instance, then it makes sense.
Or
If you store each city data in a separate Shard, then Postgresql is also good enough; it supports geo spatial indexes & queries.
If each city is a shard, then we're thinking of storing 2-3cr (20-30M) in a single table. It's something that sql reads can easily manage.
So, it boils down to companies expertise in db: sql vs nosql. Using sql makes it simple & easy to manage.
Managing C is a pain and has a huge maintenance overhead.
Eventually, they end up managing lots of DBs, say, 100k shards/DB instances. So, need to see if C can scale to have these many shards or can make it easy to manage with lesser no.of shards.
Thank you so much keerti ma'am & Gaurav bhaii... Please make video on system design of ChatGpt if possible..
Thank you
We can put Rate limiter in this system as well because might be if someone using hack script and able to swipe 100 profiles in 1 min then we have to stop it.
2mc2 would be around 2 trillion instead of 4. You'll only match two people
100 is totally fine 🤣🤣🤣🤣🤣
hello, thank you for your videos they are really useful. Are you plannig to complete software design patterns series?I guess there are only 7 videos🥲?
Hey, those are the most important ones. Which other pattern do you want me to cover? Please let me know!
@@KeertiPurswani Actually I would prefer you to cover all of them 😅 but to prioritize Prototype, Bridge, Composite,Facade and Proxy might be nice to cover. Thank youu.