CVChris Vestersincvesters.hashnode.dev·Jul 26 · 5 min readAction 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. 00
CVChris Vestersincvesters.hashnode.dev·Jul 12 · 4 min readMultiple 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 act00
CVChris Vestersincvesters.hashnode.dev·Jun 28 · 6 min readThird 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 00
CVChris Vestersincvesters.hashnode.dev·May 3 · 3 min readMail 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 ca00
CVChris Vestersincvesters.hashnode.dev·Apr 19 · 4 min readMulti-Tenant SQL QueriesIn 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 00
