Monolith Vs. Microservices + Docker + Kubernetes | Systems Design Interview with Ex-Google SWE

Рет қаралды 6,685

Күн бұрын

Пікірлер: 52

@bengillman1123 10 ай бұрын

One detail that might not make it into a quick video is that Kubernetes pods are not simply containers. Often they have multiple containers running inside of them: the main application container, initialization containers, and sidecar containers. One use of a sidecar container is for doing things like authorization, especially when using a service mesh. Your videos are super helpful btw. Thanks for creating them.

@jordanhasnolife5163 10 ай бұрын

Very cool, thanks for sharing!

@Will-dd9yc-v1z 3 ай бұрын

Holy... finally finished this monster of a series, probably the best crash course on system design I have ever seen. I learned more here than my last 3 years of CS!

@jordanhasnolife5163 3 ай бұрын

Thanks Will, glad you enjoyed :)

@Jayvil773 4 күн бұрын

Thank you for the series, finally finished it! You're a literal chad, I can only hope to grow up to be like you one day.

@jordanhasnolife5163 3 күн бұрын

You already are brother

@ashoke8031 Ай бұрын

I've been struggling for months to learn system design. Good narration all over the series! Thank you so much! Moving to System Design interview questions 2! If possible, please put a video on how you generally dive deep into a topic/technology!

@mickeyp1291 10 ай бұрын

re-kubernetes - due to docker going crazy and demmanding licenses, we actually dont use docker under kubernetes anymore. we use conternerd or other container technologies that all basically do the same thing. docker is like jeep or refrigerator, its a brand that is so powerful you use it to refer to the technology. at at&t we used a few container implementations. you can also build containers without docker. and you can run containers with many different repos.

@mcee311 Жыл бұрын

This stuff is gold. Cannot wait for the next series!

@jordanhasnolife5163 Жыл бұрын

No u

@dipsrips 6 ай бұрын

Just Finished watching my first ever System Design playlist. Huge thanks to you for taking the effort of explaining important design concepts in a fun manner. Hope to keep watching more content from you in the future.

@leonardom.deoliveira4465 4 ай бұрын

man is just the GOAT gigachad of system design huge thanks

@bokistotel 3 ай бұрын

Finally made it to the end! Thanks for the hard work!

@itshaywire_ 3 ай бұрын

This playlist is a masterpiece

@onurozer7218 11 күн бұрын

Best series ever! Thanks for every single one of them

@sahilguleria6976 2 ай бұрын

This is giga-brain system design content! Massive thanks for dropping this gold. 🙌💯

@tenthlegionstudios1343 5 ай бұрын

Great content. Just chiming in that there has been a return to the monolith, or at the very least self hosting. Example of a monolith that works, stack overflow. Even though the company is losing traffic from ai, it is a good example of a more monolithic system working. Collocating and simplicity for deployment can be super powerful. But then again, in my experience, designing a monolith that works well is hard. Usually you end up with tightly coupled code. Especially when java didn't have first class functions.

@jordanhasnolife5163 5 ай бұрын

Interesting!

@jamesmee7201 Жыл бұрын

Thanks for the great explanation of docker/kube and their relationship w one another👑. Any recommendations on how to get hands on practice with them?

@jordanhasnolife5163 Жыл бұрын

Truthfully, I think it's one of those things that you use if you have to, but you can always play around with kubernetes on your local computer, same for docker if you make a personal project and want to deploy it

@yiannigeorgantas1551 2 ай бұрын

Just finished the series, thank you so much for this!

@ovsepavakian6109 Жыл бұрын

Nice video. Technically you can scale different components even using a monolith app, just assign each service a role (upload, users,etc) and setup load balancing, so each role gets relevant traffic. Not an ideal solution, but actually used in real systems

@jordanhasnolife5163 Жыл бұрын

Fair point!

@mickeyp1291 10 ай бұрын

you're talking about a microservice that is bloated, i recently heard someone call it a federated microservice. its a common practice when you have legacy systems.

@WaffleWafers 7 ай бұрын

Just trucked through this entire playlist in the last few days to prep for interviews. Great content and you're fking hilarious man. Cheers!

@jordanhasnolife5163 7 ай бұрын

Good luck!

@mickeyp1291 10 ай бұрын

one more thing - although i agree with not rerquiring microservices in practice, make sure you use SOLID principles and break your monoloith code into interfaces and use "IOC" or dependency injection. the best way to code is through at least 30% TDD to make sure your dependency graph is the right way up. as allways loving your stuff - keep em coming.

@jordanhasnolife5163 10 ай бұрын

agreed here

@Luzkan 9 ай бұрын

Amazing content Jordan, you are just giving out an easy AOE skill level up effect to random characters over the world. After watching the whole playlists, I have a meta question - how did we come up and agree what makes X a part of System Design (assuming random bunch of people vaguely know what they are going to talk about when "System Design" keyword is mentioned). Why aren't some parts of that aren't considered lets say "Architecture Design"? How do we draw a line (or rather a gradient maybe) between an Implementation and a Design? To give a random example, why isn't an actor tracking a thing considered in System Design topic? There could be many important considerations like how to keep the anonymity of the data while still knowing how to use it, and all the other possibilities around that. But then, it seems I would bring that topic out of the blue, as it's not a "staple" one in the System Design category? IDK Thanks for your work bro!

@jordanhasnolife5163 9 ай бұрын

Hey Luzkan, thank you! To answer your question, I mainly try to cover things that are asked about in systems design interviews. If you have data that indicates that a lot of companies are asking about data privacy specifically in a general SDI, then I'd look to cover a topic like that.

@santos-samuel Ай бұрын

Dope series! Thank you for the effort in making this.

@recursion. Жыл бұрын

Excited for another Season Jordan. Also don't drink too much. ;)

@jordanhasnolife5163 Жыл бұрын

Yessir 🥰, though unlike you I don't get to live in sunny Australia

@davidrice974 7 ай бұрын

Good stuff - something this made me think of and was wondering - if you’re using a serverless compute like lambda or functions, then whether a bunch are in one repo and binary or not, they’re essentially more like Microservices since each function will scale independently of each other

@jordanhasnolife5163 7 ай бұрын

I'd agree there

@thewildnath 6 ай бұрын

Thank you so much for this whole series man!

@mickeyp1291 10 ай бұрын

really love you videos and your general vibe you embrace your inner geek in a way i never did when i was your age - re docker - you cant just scale up and down a container, that's just wrong you can scale more instaces but not change memory of cpus. min the docker installation config (vm) you can decide how many cpus and memory is alotted to the docker containers as a whole. the reason docker is fast is because instead of installing a complete virtual OS it actually uses your own OS's core and only runs containers over it. hence why linux docker couldnt run on windows nt systems before WSL, and why you cant run windows dockers on *nix systems. keep up the good work

@jordanhasnolife5163 10 ай бұрын

thanks for sharing!

@mickeyp1291 10 ай бұрын

the biggest problem about monoliths is single responsibility is broken, and very high cohesion because instead of using depndencies and interfaces correctly you just hack from one library to another due to time constraints. then its planned to decouple this functionality and time time doesnt arrive to do this, and after a few months the code looks like a spagetti of dependencies going up and down.

@andriidanylov9453 Жыл бұрын

Appreciate. I have watched all videos. Great job.

@jordanhasnolife5163 Жыл бұрын

Thanks Andrii!

@anshulkatare 2 ай бұрын

Hey jordan, The concepts of security, monitoring, logging also comes under system design? Here a company TA asked for them to consider during interviews.

@jordanhasnolife5163 2 ай бұрын

Are you asking me if they do? It depends on the role and problem I imagine, but monitoring and logging definitely could

@anshulkatare 2 ай бұрын

@@jordanhasnolife5163 Yeah, can you also make a section of the tools in this area. Like datadog, echo kibana, grafana etc. That would be a great help. Also for security things like JWT, crytography, sharing keys etc.