In today’s modern web development, the need for a robust authentication mechanism has become a common requirement. Many websites and web applications of all sizes need secure access controls to safeguard sensitive information and ensure a tailored user experience. Even in scenarios where access restrictions are not really needed, authentication can be used as a mechanism to identify and personalize user interactions to enhance user experience and engagement. Now, let’s

When I started this series of articles I had something in mind, the way the cloud companies have categorized their services marketing strategies. It was a good starting point to organize what I wanted to say, but as I progressed with the series I realized there was more I should be saying. The focus of this last article is a bit different, it has to do with what’s now being

In my previous articles we covered the general view, what you should do first and what your end goal should be. But there is one last approach to cover, what if you do not run things at all? This is what’s called Software as a Service (SaaS), you simply use services. You no longer pay for servers or licenses, you only pay for the service. In my head most clear