Відео

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🎉

Nice🎉

Seems like I came early

First viewer. Hurrah

What I like most about your videos is that they are short, crisp, to the point, great visuals and no BS

helpful but shallow. there's gotta be more details. what if the machines running the queues crash? What if publisher publishes faster than consumer consumes? what protocol is used to communicate? if multiple producers are producing, what orders are enforced?

Do we need those when using AWS or GCP?

very bad explanation. and the architecture is also not crisp. too naive

Really good explanation and walkthrough, thank you!

Very well done. Cool.

what type of education do you follow in order to know all of this stuff. its really impressive

W mans

awesome explained brother

awesome explained

Hi, I really like your channel and have learned a lot from it. However, in this particular case, I think your solution is not good enough because it mixes application with infrastructure. In this case, a Docker in Docker solution would work much better. With such a solution, you would separate the process of load balancing and providing access to your service from the application itself, for which it would be necessary to create an environment for the given language on an ongoing basis. Besides that, keep up the good work. I always look forward to your next videos!

Too much emphasis on calculations. In a real system design interview , candidates will spend 2 mins max on calculations. Anything more you are screwed

Your Channel is very good

Why not use Kafka for high through put?

I had insomnia, but now, thanks to the vlog, I fall asleep within minutes watching the videos!

What software are you using on your iPad to draw and record?

thank you.

what is your work experience?

love this type of content! looking forward to more