Bulkhead Pattern - Fault Tolerant Microservices

[@king0s]

One of the only Indian tech channel that I would say is top notch. I try to watch only non Indian tech channels though am Indian because I feel Indian youtube channels they focus more on making things look complicated as possible and using jargons over that to make the learner feel overwhelmed. But this channel is the only Indian channel I just love because every explanation is built from scratch right in front of you with easy to follow visuals, and the explanation blossoms spontaneously. You rock Vadgama bro. I have said it many times before, will say it again in future- I am so grateful for finding this channel.

[@coolcoolj0102]

I see Defog Tech video, I upvote

[@NamanSaxenaa]

Pure genius! Buddy your videos are gold.

[@Timjstewart]

Beautiful description of the pattern!

[@dhirendrakumar4619]

Bhai Bahut sahi samjahte ho i love the way you make us understand

[@SS-eu4eb]

Thanks for clear and concise explanation.Great video!

[@VijayaBhaskaraReddyKalluri]

Very Good Explanation , thank you !!

[@ChrisAthanas]

Very clear explanation of a complex subject

[@cantwaittowatch]

thanks for explaining this concept with great clarity, detail and fluency

[@khushbookaur]

Such clear explanation

[@exploringBees]

Thanks a Million ! All videos in this channel are just wow ... Can you please make video on Concurrent HashMap internal working ...

[@raghavendrachamarthy6921]

Nice one...this is much easier using the microprofile tolerance library...

[@silentsudo]

Thanks, your videos are motivation to implement a POC for my blogs.

[@AmarSharma222]

Thank you for uploading the video. Very clearly explained.

[@douglascavalcante7624]

Thanks for your video!

[@slraja83]

wow, clear and concise .. please keep doing more videos !!

[@theexposerprint7574]

You are awesom. I need a mentor like you

[@shirish2005]

please keep adding more videos

[@ShivManiShivraj]

Good information .. Keep doing good @Defog Tech , Could you please make a video on EventDriven concept in microservices.

[@DefogTech]

Sure, that's a good idea. Thanks

[@johncerpa3782]

Great explanation!

[@SiddharthKulkarniN]

Good explanation! Thanks for posting.

[@tejasdoond7614]

A very good video sir. Thanks a lot

[@DefogTech]

Sir, you should critique my videos instead of thanking me. Allow me to learn and grow :)

[@romantsyupryk3009]

Thanks so much for this tutorial.

[@deepakjain5947]

First and foremost, great video series and explanations. Thanks a lot. I was looking for a good source of info on microservices and you have nailed it. Couple of questions on your video: 1. Isn't bulkhead pattern similar to the circuit breaker pattern that you mentioned in another video? Instead of number of failures, now the factor is resource usage. 2. As a design pattern, which one is generally recommended for a service: To have a threadpool in a single service or have multiple instances of a service with a single thread in each? Thanks in advance for your responses :)

[@DefogTech]

1. Circuit breaker is used to help the other service return to normal while bulkhead us used to protect current service use only limited resources. 2. Ideally even with multiple instances of a service it's good to use threadpools in each instance though need to set count accordingly and if required use external service like redid for coordination

[@Pankajrealistic]

Your explanation is awesome..but one thing i want your example code for every tutorial that will help us practically more .!

[@nitinaljapurdata4668]

Awesome explanation. Could you please make videos on design patterns

[@navinahmed]

You make amazing videos buddy. And it is very much what I need. I actually wanted to ask you on how your bring up processes in case of a fail over scenario.

[@DefogTech]

Do you mean when a process stops responding to any requests? I think health-checks will help in that case (eg: by Load Balancer). All load balancers have active healthchecks which avoid requests going to failed process. Then its upto your alerting systems to know process is stuck and needs a restart. Process itself won't be able to perform any function.

[@navinahmed]

@@DefogTech there will be active requests being processed. While processing these requests, suppose the server goes down. We will have to handle the fail over process and start the same processes from the failed stage in another server. Ps :These are asynchronous requests. So the client will not be waiting for an immediate response.

[@DefogTech]

That state of processing will need to be saved externally so that next process can continue. Example if request is taken from queue use transaction where only if request is processed successfully the message is acknowledged

[@navinahmed]

@@DefogTech thanks that was the plan. To save it in a database. And if some servers fail, all failed processes have to be rerun. Right?

[@DefogTech]

Correct.

[@ghsi10]

You got race case in the first example, you should change int to AtomicInt

[@Vinod007ism]

Brother, Why you don't make videos now?

[@salahayman3513]

please add video on handling concurrent transactions in spring boot and micro services thanks

[@rockyrocko-j2gk]

Does the Resilience4j manage Tomcat main ThreadPool settings based on the configuration we are providing while creating bulkhead or do we have to make sure on our own to keep the total and thread count for each bulkhead to be less than or equal to the total ThreadPool size of the Tomcat?

[@vishnugovindan8550]

Quick question: If threshold is 3, and 3 threads have gone into wait state as the other service is not responding, any further requests will get a default response? But what about these 3 threads? Are they released after some time out and then how is the count maintained then? Also, I'm kinda confused how this is different from Circuit Breaker. They both are keeping track of a threshold and returning default responses till the other service is back.

[@sumitbasu5146]

Could u please make more videos🙏

[@vidyasagarvenkatachalam1243]

Thanks for the video! I need a clarification. Bulkhead pattern and circuit breaker pattern are two different solutions to prevent the same problem (i.e. a microservice, say, an order service becomes unavailable after sometime if another service, say, payment service takes too long to respond to the requests from order service.). Is my understanding correct? If my understanding is wrong then please explain the difference between the problems prevented by the two patterns.

[@deepaksolanki1972]

Nice explaination. Can we get this file as notes?

[@runnerup15]

Is this what happened with that aws us east issue last month?

[@narayanadhurti1603]

Can you please update the videos to the current year.

[@DishariDe]

Could you give some pointer as to how to design a distributed bulkhead config?

[@1beero]

is there an available github repo to show this in action at all please?

[@vikaskokae]

Just as i was watching the video and reached half way, did i realise the significance of automated unit testing for such scenarios. Most of us would design the system, as per access patterns, but how many go out of way to automate testing for them.

[@StyleTrick]

The content you put up is amazing! Just out of curiosity, how do you learn all these new patterns. Do you implement these at your job etc? I assume you work as a software developer correct?

[@DefogTech]

Yes, I work as software developer, but unfortunately don't get to work on any good technologies shown in the videos. I just read a lot and try to stay relevant, and have recently started to put that into videos. Hope it's helping

[@StyleTrick]

@@DefogTech That's awesome that you stay up to date. What resources do you use to do this? Also don't mind me asking, what tech do you use at your role?

[@amitmahajan3115]

Wait why can't we use Async calls in this case?

[@samantr]

Would sidecar proxy technologies like istio handle these issues better in Microservices .. instead of handling it in business logic layer ?

[@DefogTech]

Absolutely. Though, istio is not yet integrated within many PAAS platforms. Its currently only available for K8s. With servlerless and cloud, slowly all these patterns would be available for developers to configure.

[@samantr]

@@DefogTech Thanks for double defogging it :) Btw just watched your another video (kzbin.info/www/bejne/h5q7fGN4bqubhZI) that explains this nicely ! Thanks a ton .. keep up the good work sir !

[@dataguy7013]

@Defpg, great video.Is bulkhead pattern implemented in Service Mesh or API Gateway? Can you explain?

[@DefogTech]

Its a general pattern that can be used in both

[@大盗江南]

Could u plz do a video about how to calculate internet traffic? For system design purpose, one of the step is to calculate the volumnes, eg a video usually takes 1000 MB for 10 min... etc... A text how many bytes etc... Thank you!

[@DefogTech]

Thats a good idea. Will add it to my TODO video list. Thanks!

[@大盗江南]

@@DefogTech thank you 😄

[@PiyushSingh-vx7bx]

🔥🔥🔥

[@JettZheng]

the problem of this pattern is how do we decide the concurrent call number? It seems like we need to estimate according to all downstream microsevices,and allocate to each remote service some resource, which means this service is strong coupled with downstream service right?

[@DefogTech]

true, but once you decide to call a microservice it is a dependency required to fulfil a function, so its not strong coupling because in the future the microservice being called can be replaced with another one with same API

[@JettZheng]

@@DefogTech I got your point,thanks for your explain ^_^

[@ChittipoluSA]

Can't use semaphore for this use case instead of third parties library?

[@DefogTech]

yeah, sure can, internally these libraries must be using something similar.

[@ChittipoluSA]

@@DefogTech thank you so much for response.

[@rishiraj2548]

🙏

[@AnkitaNallana]

why do you have subtitles disabled? why why why

[@DefogTech]

I haven't disabled it. The video is not popular enough for KZbin to generate one I suppose.

[@codegeek8256]

Who owns this channel? Will it be active again??

[@DefogTech]

I own it. It will be active again I promise :)

[@TheDavBag]

go semaphore =)