Learn Java and Programming through articles, code examples, and tutorials for developers of all levels.
Top 70 Java Interview Questions for Junior Developers [1 to 2 Years Experienced]
Difference between save(), saveOrUpdate() and persist() in Hibernate Session
15 Technical Core Java Interview Questions Answers for Experienced Developers
Top 21 String Programming and Coding Interview Questions With Solutions
When You should Not use Microservice Architecture? (Answer)
Hello guys, recently while giving interview in one of the big US based Investment bank I was asked about, what are the scenarios when you shouldn't be using Microservices architecture? When I hear this question I was big surprised not because I didn't know the answer but because most of the people ask about using Microservice architecture and this was the first time I am hearing otherwise. To be honest, it's a good question because most of the candidate will prepare about benefirst about Microservice architecture and they may not know when it's not appropriate to use it. Since I have worked in low latency high frequency application, I knew that multiple process means more latency so clearly a Microservices is a big no if you are working on a high frequency low latency application. In those cases you want to do all your calculations inside a single thread or process without even swapping memory to avoid delay. Hence the first answer to this question was, you shouldn't be using Microservice in a low latency application.