I love the cute computer in the background

no complaints other than the font used in the canvas.

I think more detail could have been given on why you used Kafka. I understand how it makes sense, but maybe walking through a couple data flows would have made it more clear.

I'm not trying to be difficult, but I don't understand how using a bearer token or jwt is any different / better than having the user send their username and password with each request. If the bad actor has a way to see the request, they could just copy and use the token, just the same as they could copy the username and password, which needs to be sent to create a token to being with. I think this is why using HTTPS is so important.

Can you name some of these traditional message queues?

during the process of notifying the driver to either accept or deny why not send to lets say 5-10 drivers closest to rider and the first to accept gets it and all the responses sent to a queue and if theres a driver for the driver the rest get rejected for that trip , this would improve user experience as users would spend less time searching for a driver instead of waiting for 1 drivers response then switching to the next which can take up some time

This is a great video for large distributed systems.

Wow👏👏👏👏👏👏👏👏 nailed it 💯👌

imho, the downside of the timeseries db is that you will repeat calculations every time you want to know the total downloads or the top ones. In that case, I would have stored the data in the database on a field that counts the total downloads and then search from there. The issue in this case is that you will probably have deadlocks or concurrency problems because of the reads and writes, mostly on the top used apps. in this case, the db should be sharded so reads occur in one db shard and writes on the other ones. then automatically the db will update the data from one shard with the other ones. Aside from that, great design and i think the combination of db and elastic is a great choice

Explanation is good but Its not comprehensive. One can't quality a system design interview based on above video for the given topic.

Doesn't this design make Kafka the bottleneck for the whole architecture?

What kind of terminal do you use?

annnnnnnnnnnnd you infra cost will be 50k and need engineers worth 200k for maintainance

This guy is talking like Sidhi baat no Bakwas.

Oh put their data center in the damn Ohio lmao, fire content btw

Very impressive

This seems like a video designed to make people fail system interviews. "Kafka," "load balancer," "websockets" are generic system design concepts you are randomly tacking on.

A

I'm not sure if I understood correctly but why are we not using any ES cluster to speed up our search? No DB can be as efficient as ES when it comes to search.

🔥🔥

I feel like this is useless because you just tell us the answer, how and why.

Remember that you have the power to control your thoughts and emotions. Choose positive thoughts, practice mindfulness, and let go of negativity that doesn't serve you.

What is the name of the pen softwere used for explaining on the screen?

I feel it doesn't make sense to put chunks in queue, direct client having access to a messaging-queue-system is not practically good idea from security perspective. Also it doesn't reduce load anyhow as messaging queues also need to be scaled if not injestion servers, so it is just adding extra layer just for the sake of adding. Correct me if I am wrong.

Can you do a design for versions control system?

Good explanation

Hello! Which app do you use in your iPad to draw diagrams and explain the concepts? Great video! 👏

Why not enable RAID and set the correct level?

You always need to think about replicas

nice

Its nice you showed both options using JWTs and simple session IDs. I see lots of people jump straight for JWTs because its newer, without thinking about the actual pros and cons. Generally the first question should be *can* your system actually do stateless authentication? For many financial services for example, a business requirement will be instant reflection of updates to permissions or session revocations - to implement this in JWTs you need to constantly check a blacklisted token table - immediately nullifying the benefit of stateless auth. There's also the question for many apps - realistically how many types of action can the user make anyway that won't be hitting the database / reddis at some point already? Considering the complexity that can come with JWTs, for simple apps I often find myself reaching for session IDs first, with certain components using stateless. I've yet to work in a company where even a few minute lag between permission updates is acceptable on the app itself. There's also some hybrid patterns, the satellite app authenticates with an internal auth server, recieving a JWT. That JWT is then hashed into reddis as a session token, and sent to the user for user <-> api auth. It's important people actually ask these questions to the interviewer before picking their solution!

Sir, this is golden. Thank you!

Here are some of the issues in this design. 1. The cache and timeline construction are the most difficult to solve, yet we know too little on how it is arranged 1.1. Sure, if you have only 2 users, it will scale well. But, what if you have 180M followers to Musk? Will you fan-out 180M cache and database updates for a single tweet? 1.2. It completely ignores geography. What if the DB shard for Elon is in Texas and his followers are spread across the world? 1.2.1 Where do you store data for a user from a specific country? What if they travel? 2. Social graph. 2.1. It sounds like on every tweet write, you query the social graph to figure out where to fan out. How does this work to scale? How many shards do you need to read to know even where to fan out too? 2.2. What if a user unfollows? 2.3. Where is the graph stored. The design presented will not scale well to the millions and billions of users.

Client supplying timestamp "is a bad idea. Let's do it anyway"

Awesome, which software do you use?

Thanks for the video! which platform are you using to note?

Thanks, I really like the videos! But (in my personal opinion) it would be much easier to perceive information if you took some pauses when you speak. Otherwise, videos are really helpful! And one of the topics I would love to know more about is how systems like Apache Spark or Hadoop work internally, what are the specific use cases and etc. Thanks again!

I'm dumb so any help would be appreciated. Why are hash join on 100 rows tables faster than hash join on 10 rows tables ?

Thank you for sharing this! This seems to be a common system design problem. I've gotten a variant of this at least twice now from companies that I've been interviewing with

would you be available for consulting

I feel like my Pokemon is about to evolve!

🎯 Key points for quick navigation: 00:00 *📚 What is a database and how queries work?* - Database takes in SQL queries to retrieve data. - SQL is declarative, focusing on what data is needed not how to get it. - Internal complexities of a database translate declarative queries into execution steps. 02:09 *🧠 Process of executing a query in a database* - Database query process involves parsing, query planning, and execution. - Parser translates SQL query into a data structure for the database to use. - Query planner optimizes query execution and evaluates different plans based on database characteristics. 03:32 *🔍 Role of parser in database query execution* - Parser converts raw SQL text into a parse tree for easier database evaluation. - Parse tree organizes query components like select, from, and where clauses for database use. - Use of parse tree allows the database to recursively evaluate query components. 08:12 *⚙️ Query planner in optimizing database query execution* - Query planner considers table statistics, cost constants, and available indexes for query optimization. - It generates multiple plans, evaluates costs for each, and outputs the most efficient plan. - Optimizing query planning leads to faster and more efficient database query execution. Made with HARPA AI

This interview misses critical discussions about the way we send new tweets to the user. I think this system doesn't work as expected. specially having a limit list in Memcached. For example, what if someone has 30 million followers?

Your videos are very helpful and to the point.

Solve the payment processing by switching to bitcoin only payments.

Awesome thanks a lot

how algorithms works video plz

Thank you a lot for your video. Maybe next time tell us about the pros and cons of SQL? For example, that is invented in the 80s and that it is ineffective when working with a large amount of data?

CS degree help me understand it pretty clearly. 😅

Nice🎉