Search for a command to run...
For a project where I want to be able to offer more interactivity and concurrent modifications, I decided to use a WebSocket. Since my backend is written in Spring, after some research, I decided to u
When I designed my action object system, I only imagined the possibility that an action would impact a single entity. In the end, this is what you also would imagine with a traditional REST endpoint.
In a previous blog post, I introduced my new approach regarding updating objects. Instead of just performing the updates in the service, I approached it in a true object oriented approach and made act
In the previous blog post, we discussed whether or not you should offer a separate public API. One of the points there was how you do the authentication, and whether that should be done in a separate
I am a big advocate of keeping all translations in the front-end part. This becomes tricky when we have to deal with sending e-mails. The front-end is not able to send e-mails and thus the back-end ca
In the world of cloud applications, having a multi-tenant application is standard. While there are multiple options to implement multi-tenancy regarding the database/storage approach, having a single
Everyone agrees with the fact that having some global state is a bad idea and should be avoided. The cases in which this is really the only option are very limited. One case however, is in Spring wher
In Java, we have two types of exceptions, checked exceptions and runtime exceptions (I am not including the Error class). The only difference between these two types, is that the checked exception is part of the signature of the method and must be ha...
When designing an API, we tend to only focus on successful requests. This often leads to error responses that are not useful and often don't contain any information. I am guilty of this myself, and in my own projects I typically only use the HTTP sta...