JVM Spring applications are very flexible in handling different environments. You can handle multiple brands like
subsidiary companies or different target environments like
development in a very simple way.
This could be necessary when environments behave differently from each other or have to connect subsystems in other ways.
Generally, you do not want to use If-Else constructs in such cases. To handle these issues, the Spring Framework has an
elegant solution called profiles. With these Spring profiles you can run the same build of an application on various
environments with just a few additional JVM parameters.
One of the principles of Kanban is to pull work, instead of pushing it to the next process step. I have written about how we have implemented the pull principle in Jira boards in 2016 and 2017 (both German). This post summarizes our current implementation in English for those who don’t speak German.Read more »
Objects in JSON:API format have proven themselves as a standardized data exchange with REST. Error handling can also be managed uniformly with JSON:API error objects. Spring Boot offers a standard JSON format for error attributes. In this article, we look at how to change the Spring Boot Standard JSON format to a JSON:API Error Object format. As a bonus, we also find out how the JSON:API Error Object can be displayed instead of the Whitelabel Error Page.Read more »
console.log in the browser.
It is the easiest way to get information about the code and helps the developers, when they are debugging a problem and don’t want to use the
debugger because they don’t want to dive too deep into a framework like Vue.js or have any other reason.
But there is more than the
console.log command and in this article we will look at these other options.