In general it is a very simple pattern. You just wrap your function/method/behaviour with another function which keeps track of the failures/success of the that function (service/DB calls) and opens or closes the circuit for you. Sounds simple enough. It is simple.
I have been learning and playing around with GoLang lately and it seem to be fun. At first being a Java developer it looks weird and complex, but once you start playing around it is quite fun. Why did I start learning Go ? - I read a lot about its features like being… Continue reading Quick to digest cheatsheet – for GoLang
Testing is one of the most critical parts of the Software Development Lifecycle. Writing meaningful unit/integration tests with enough coverage is really important. It saves your system from critical bug injection, helps meeting functional requirements and gives clear understanding of what the software component is doing. Unit tests can also be performed by mocking… Continue reading Integration Testing with Test Containers
Hello! Welcome to the part-2 of "How search engine works" series. Previous part was all about the basic concepts that go behind a search engine at a low level. If you want to refer the previous part, feel free and read it here. This part will be focussed on how things work in elastic search… Continue reading How search engine works ? Elastic search – (Part-2)
Hello, welcome to the second part of "Parallel Programming in Java" series. If you have somehow missed the first part and want to read it now, then read it here. So Part-1 covered the very basic concept of task execution in parallel and how ForkJoin framework helps in writing parallel programs easily. We saw how… Continue reading Parallel Programming in Java – (Part-2)