Great video, but I think it would be good if you mentioned some of the pitfalls or common issues with each of these approaches, in addition to the things they can benefit
The Ambassador pattern is not typically associated with reducing latency since it introduces an extra component into the communication process between services. In fact, service mesh providers like Istio are often recognized for the latency overhead they contribute.
I think it reduces latency in the event where the busy CEO is doing something else and the other part has to wait for the CEO to handle its request. The ambassador can start handling the request immediately.
In my opinion one of the most important and most used patterns wasn't mentioned here: Job queues (work queues + worker pool). Basically you have a queue of jobs to be completed, and several nodes are working, and when one becomes available (i.e. finishes its previous job), a pending job enters that node. Like a single queue in a shop waiting (=all the pending jobs) and a few cashiers handling them one by one (=the workers). The difference from pub sub is that only one node gets the job, since there's no need for multiple nodes to handle the same job.
Awesome video. One suggestion to improve it more. 1) Keep Header for each section on top. Example: When explaining Sharding, It will looks good if Sharding is there in full 10 second section
Fantastic! Best event-sourcing explanation ever! I tried to know what event sourcing is many times and understand only from this video, that I actually worked with event sourcing many years when worked with accounting software. Thanks a lot!
Amazing. Thank you! Please keep on create such kind of videos. The selling point of them is a shortness, them fit perfectly in time gaps and allows to become better without rearranging a schedule of a day.
I think that Replication should be in the list as one of the most important patterns in distributed systems. Optional: quorum, fencing, eventual consistency, you name it
2:49 "When each commit represent a change" - well, in Git each commit represent a snapshot of a filesystem. Diff between commits represent a change. I'm boring, I know.
This video is a bit of a mixed bag in sense of patterns. While Ambassador and Circuit breaker are surely patters of distributed and distinct systems, CQRS and Event Sourcing are typical examples of how to architect a single application (system).
Thanks for creating such good content Alex! I have two comments though.. 1. It's not good to have advertisement video names like this one, especially when the target audience are educated people. I mean based on what statistic you stated that these are the top 7 most used patterns? 2. In CQRS part, I think the below example you gave is irrelevant. "separate list items (reads) and new orders (writes)". Orders and Items are different domains and they might be in different microservices and also both of them might implement CQRS separately (orders service might have one DB for write and other one for read and same applies to Items). Good example would be: a banking application let customers create banking accounts(writes - less frequent) and to retrieve accounts (reads - more frequent).
What pattern or strategy can I use for a website that sells tickets for movie theaters?, for example if a user selects seat 1-A he's given 5 minutes to complete the process and buy the ticket, I assume that in those 5 minutes the seat cannot be selected and buyed by another user, I'm not really sure if that's the way the website should behave or if another user can buy a ticket for the same seat. Taking it a little bit further imagine that user can buy tickets using a website, an app, and directly in the movie theater.
Chatgpt uses something similar to CQRS right? The AI doesn't learn with our input. Its learning process is verified by an employed before being accepted to the AI
This is too high level and too abstract. Would be great to expand each one. I found most of the top x videos are hard to digest. In 5-7mins, it will be great to dive deep into one topic and explain it well
I see an opportunity to convey a different message to early career engineers by portraying the busy CEO as a woman, rather than the executive assistant as a woman.
@@shaleensaxena1664 create a diagram with the system configuration for your toy system and list the tools you would use(eg elastisearch, kafka). Browser their sdks or learn those technologies depending on your current level of knowledge. Then all but left to build it depending on your choice of programming language. You could actually learn the technologies like kafka while coding the application. Happy coding
Whoops, you accidentally set the CEO as male and secretary as female. Would be great to fix your bias in future videos. It would suck to take away from your great content.
How to make ads and people don't understand this is ads. Brilliant work) almost 0% real and applicable knowledge, not include PostgreSQL in sharding?) I even don't understand who is this guy and what he did and why all of you listening to him)) it's literally copy paste from books) most of this info is 90% not used widely only used for interviewing jobs. Real things are much ugly everywhere, I thought your glasses will be pink LOL)
I don't understand your gripes with the video. It introduced 7 distributed systems patterns. If any of them seem applicable for your project, then now you know what pattern to go in-depth into. They even named commonly used services that utilize/offer these patterns. I agree that real projects are often not as well-executed as the theory, but I feel like you learn the ideal/theoretical design to then make the necessary compromises based on your project's limitations.
I have used all seven of these patterns (+ strangler fig) in production systems. Although I would not refer to them as "patterns". of course this is an advertisement for the books and newsletter. i own both of the books and found them to be quite valuable. The intended audience is not for complete begineers. I like short videos like this too. They are nice little refreshers
@@casiowatch125 "I have used all seven of these patterns (+ strangler fig) in production systems" size of prod, not in DB size but in actual services or users size?
I watch all his videos on 1.75 and I swear this is the very best system design tutor on TH-cam !!!!!
Great video, but I think it would be good if you mentioned some of the pitfalls or common issues with each of these approaches, in addition to the things they can benefit
In 6 minutes? 😅
Who said it had to be done in 6 minutes?
I think the purpose of this video is just to introduce into the pattern logic.
The Ambassador pattern is not typically associated with reducing latency since it introduces an extra component into the communication process between services. In fact, service mesh providers like Istio are often recognized for the latency overhead they contribute.
I think it reduces latency in the event where the busy CEO is doing something else and the other part has to wait for the CEO to handle its request. The ambassador can start handling the request immediately.
Every arch has its own pros an cons. API Gateway provides us flexibility over 3-10ms depends on what kind of controls we add to the flow.
In my opinion one of the most important and most used patterns wasn't mentioned here: Job queues (work queues + worker pool). Basically you have a queue of jobs to be completed, and several nodes are working, and when one becomes available (i.e. finishes its previous job), a pending job enters that node. Like a single queue in a shop waiting (=all the pending jobs) and a few cashiers handling them one by one (=the workers).
The difference from pub sub is that only one node gets the job, since there's no need for multiple nodes to handle the same job.
Awesome video.
One suggestion to improve it more.
1) Keep Header for each section on top.
Example: When explaining Sharding, It will looks good if Sharding is there in full 10 second section
Fantastic! Best event-sourcing explanation ever! I tried to know what event sourcing is many times and understand only from this video, that I actually worked with event sourcing many years when worked with accounting software. Thanks a lot!
I view this as a jumpstart into a topic. Enough to get me going. For that I appreciate the work.
beautiful video, just loved every bit of it.
awesome! what tools do you use for drawing the beautiful diagrams? I like them so much. It makes knowledge easier
I'd also like to know. The animated reveals make it so much easier to follow.
They are mentioned in the description
Amazing. Thank you! Please keep on create such kind of videos. The selling point of them is a shortness, them fit perfectly in time gaps and allows to become better without rearranging a schedule of a day.
Incredible you just made it so simple to understand Thank you
I think that Replication should be in the list as one of the most important patterns in distributed systems. Optional: quorum, fencing, eventual consistency, you name it
agree
Replication is not a pattern, but one of the implementations for CQRS.
Good resources. Didn't know that all the pattern names but I have use some of them already.
These videos are great, thank you for making them. What software do you use for your animated graphics?
thank you, you're great as usual
Great videos and clear communicator! What video animation software do you use to create them?
2:49 "When each commit represent a change" - well, in Git each commit represent a snapshot of a filesystem. Diff between commits represent a change. I'm boring, I know.
Thank you, very useful information
Superb explanation
Very well demonstrated.
Like this nice and smooth animation chasing explanation run
Thanks again and always.
This video is a bit of a mixed bag in sense of patterns. While Ambassador and Circuit breaker are surely patters of distributed and distinct systems, CQRS and Event Sourcing are typical examples of how to architect a single application (system).
thanks for the great video!
Great video! Please, let me know, how do you make this presentations?
Appreciate your work. Thank you for clear content!
Thank you very much!
Nice video!
I love your content.
I would like to know which tools do you use to make those videos?
Would like to know more the diff between Event-driven system vs Message-driven system.
Best video nicely explain🎉🎉🎉
Thanks for creating such good content Alex!
I have two comments though..
1. It's not good to have advertisement video names like this one, especially when the target audience are educated people. I mean based on what statistic you stated that these are the top 7 most used patterns?
2. In CQRS part, I think the below example you gave is irrelevant. "separate list items (reads) and new orders (writes)". Orders and Items are different domains and they might be in different microservices and also both of them might implement CQRS separately (orders service might have one DB for write and other one for read and same applies to Items).
Good example would be: a banking application let customers create banking accounts(writes - less frequent) and to retrieve accounts (reads - more frequent).
Great Video
Thank you.
Excellent
I am big fond of your content! However i am still not able to digest that EventSourcing is distributed architecture pattern😮 please guide us
I cant wait for my database to shart itself.
Impressive
Could you please share the insights of QR CODE and How it works?
Hi. What do you use to create these presentations/animations. I'd like to use it for my interviews. Thank you.
How do you make animation in the video , it is very nice, I want to learn ,please share me the way
Is using a queue with large retry time would be considered as a circuit breaker?
What pattern or strategy can I use for a website that sells tickets for movie theaters?, for example if a user selects seat 1-A he's given 5 minutes to complete the process and buy the ticket, I assume that in those 5 minutes the seat cannot be selected and buyed by another user, I'm not really sure if that's the way the website should behave or if another user can buy a ticket for the same seat. Taking it a little bit further imagine that user can buy tickets using a website, an app, and directly in the movie theater.
is sharding the same as chunking?
Chatgpt uses something similar to CQRS right? The AI doesn't learn with our input. Its learning process is verified by an employed before being accepted to the AI
what's the diagramming tool that you used for the video?
which tool you are using for creating slides ?
how to you create your info graphics?
More examples and breakdown would have been even better.
Kubernetes does not use Envoy natively. Istio does.
Isn't rate limiter also a very common distributed systems pattern?
CQRS
This is too high level and too abstract.
Would be great to expand each one.
I found most of the top x videos are hard to digest. In 5-7mins, it will be great to dive deep into one topic and explain it well
I see an opportunity to convey a different message to early career engineers by portraying the busy CEO as a woman, rather than the executive assistant as a woman.
most best complex systems deterrent is k.i.s.s. or go home and stay there
tired of your distributing of your loads onto people
well, have skill or be evolutionized/darwinized, survival of the fittest, like you animals like to call it, and make it so
yeah you do it, not others for you, tired of that distributed smuggling system
none of you actually do anything (useful)
and no, you defining yourself useful does not make you useful, this is not useful, stop talking, do something
hello :D
Is there a way to actually build and try such patterns? I understand better by doing.
Yes! You could totally build a toy system for it. It could be only code or only diagrams. Which suites you best!
@@shentot6 I would prefer to build a toy system. Any suggestions or guidance on how to get started?
@@shaleensaxena1664 create a diagram with the system configuration for your toy system and list the tools you would use(eg elastisearch, kafka). Browser their sdks or learn those technologies depending on your current level of knowledge. Then all but left to build it depending on your choice of programming language. You could actually learn the technologies like kafka while coding the application. Happy coding
Alex, felt too quick
Whoops, you accidentally set the CEO as male and secretary as female. Would be great to fix your bias in future videos. It would suck to take away from your great content.
it feels like you don't know what you're reading sometimes.
Are you talking to yourself?
First? :D
How to make ads and people don't understand this is ads. Brilliant work) almost 0% real and applicable knowledge, not include PostgreSQL in sharding?) I even don't understand who is this guy and what he did and why all of you listening to him)) it's literally copy paste from books) most of this info is 90% not used widely only used for interviewing jobs. Real things are much ugly everywhere, I thought your glasses will be pink LOL)
I don't understand your gripes with the video. It introduced 7 distributed systems patterns. If any of them seem applicable for your project, then now you know what pattern to go in-depth into. They even named commonly used services that utilize/offer these patterns. I agree that real projects are often not as well-executed as the theory, but I feel like you learn the ideal/theoretical design to then make the necessary compromises based on your project's limitations.
I have used all seven of these patterns (+ strangler fig) in production systems. Although I would not refer to them as "patterns". of course this is an advertisement for the books and newsletter. i own both of the books and found them to be quite valuable. The intended audience is not for complete begineers. I like short videos like this too. They are nice little refreshers
I think you're missing the point of the video, if I'm understanding you correctly (which is hard with such an incoherent comment)
@@casiowatch125 "I have used all seven of these patterns (+ strangler fig) in production systems" size of prod, not in DB size but in actual services or users size?
@@ordinarygg my team handle ~80 services
Business 12m+ users monthly
Great video