Moving from monolithic applications into microservices is current trend in software design. Let’s identify some pros and cons of both architectures and challenges one may face during the system transformation.
Job is not a place for feats. But sometimes you have to be brave to overcome and complete that others considered impossible.
Defining error format is important part of REST API design.
Spring-Boot and Spring Security provide pretty nice error handling for RESTful APIs out of the box. Although it has to be documented, especially when contract-first approach to API design is used.
It is good idea to follow some common format for error responses. But OAuth2 specification and Spring Boot format may not satisfy those requirements.
How did you know that your site is down? From your customers? Then it’s time to start using some external monitoring tool.
A must-see speech by Robert “Uncle Bob” Martin on programmers responsibilities in digital world and 9 principles every programmer should follow (“The Coders’ Code”).
There are different points of view on how logging levels should be used in code. I will share mine.
My assumption is: “There should be no errors in logs when everything is fine.”
One of the challenges for start-ups or any new project is to reduce the amount of work while still delivering a full-featured product. Agile methodologies address this challenge on the project management level. Let’s discuss another approach to address it on the architecture level: UI-first development.