Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview book series. This channel is managed by Alex Xu and Sahn Lam.
To master system design, get our 158-page System Design PDF for free by subscribing to our weekly newsletter (10-min read): bit.ly/3tfAlYD
Take our system design online course: bit.ly/3mlDSk9
Пікірлер
amazing video, thanks for that!
The value your chanel is providing is immense.
Code style != Code structure, always remember to make your code extensible and maintainable with design patterns
Very glad I found this channel. It looks like exactly what I need as a computer science student / future software engineer slash developer.
In the VIPER title, you misspelled Entity as Entily
More detail please. A series would be good describing each and every nook and cranny.
My question as a fairly new beginner... how on earth is this "optimized"... Is it just me or i feel like big tech companies try to overcomplicate things on purpose
Please keep in mind that using filters inside the header and not the body might result in many url length related limitations. On the other hand using filters in body will not allow to preview directly the result in a simple browser GET navigation. Most likely a decent solution would support both simple filtering via a query string format inside url but also a more advance filtering via body. This is important when you application has complex filters or multiple filters. EG1: multiple filters with multiple options where you might hit a limit unless you defined an encoding to represent a set of multiple filters being selected. EG2: a business oriented app where the user needs customisable filters and grouping of filters with AND / OR between them like (filter1=A or (filter2 = b and filter3=c)). Users might end up with really long filters that might not be easily serialisable in an URL , keep human readability AND size constraints.
Is this how pgp sso work?
Wao, I was struggling with the basic concepts of oauth2 for a long time. This video explains it really well.
Very Well explained.
You aren't gonna need it 😂😂
I used to think after TCP Handshake we start transmitting data and I forgot about the other two steps (Certificate check and Key Exchange). I was wrong(((( Thank you
What a video!!
I agree with all of these, but as a short this obviously lacks depth. Async logs are bad, if you logs are important and would be gone if the app crashes. So if you need to optimize it, maybe send them async to another system and make it 'their' problem. Caching is very good, cache invalidation might be the hardest thing you ever have to do, so only cache what you absolutely need to speed up and only implement it after you figured out when and how cache needs to be flushed