Especially if you are developing Micro Services using ASP.NET Core, then you can shove your service into a docker container and deploy it to Kubernetes. Kubernetes then handles health check and self-healing bits (circuit breaker, bulkhead etc). However there are also third party "Service Mesh" apps like LinkerD, Polly which allow you to offload these additional requirements (they take the responsibility of retry on failure, health check, self recovery etc), so I am still not convinced about blindly jumping in. As it is with software, I have always found that the latest and greatest wants to be adopted without any thought as to whether it's "really needed for us, and is it enterprise ready and meets all our needs". Cargo cult mentality. If Netflix did, then so should we. So we blindly add Hystrix to our application stack

There is a fun video by a chap named Daniel Bryant titled "The Seven Deadly Sins of Microservices". It's a good watch

Leave a comment: