First WebSocket & Stomp ExperienceFor 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 u1Aug 9 · 5 min readcvesters.hashnode.dev
Action ContextWhen 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. Jul 26 · 5 min readcvesters.hashnode.dev
Multiple Inheritance ActionsIn 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 actJul 12 · 4 min readcvesters.hashnode.dev
Third Party AuthenticationIn 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 Jun 28 · 6 min readcvesters.hashnode.dev
Mail Languages/TranslationsI 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 caMay 3 · 3 min readcvesters.hashnode.dev
