Software And Architecture

Introduction For many years, we have been dealing with memes like try{ doSomething(); }catch(Exception ex) { println(getSolutionFromStackoverflow(ex)) }finally { testAndApplyThefix() } fun getSolutionFromStackoverflow(val ex:Exception) { curl get stackoverflow.com?q=ex.message ... } where the developers run into an error, they immediately lookup the exception in stackoverflow.com and get the solution and validate and close the error. This is a real one that is available from drop.com The original stackoverflow blogpost is here:  https://stackoverflow.blog/2021/09/28/become-a-better-coder-with-this-one-weird-click/ Looks like these will be part of a developer toolset in the near future

User Authentication in Multi-Tenant SaaS Apps Introduction We will cover few scenarios that we can follow to perform the user authentication in a Multi-Tenant SaaS application. Scenario 1 - Global Users Authentication with Tenancy and Tenant forwarding In this scheme, we have the SaaS Provider Authentication gateway that takes care of Authentication of the users by performing the following steps Tenant Identification User Authentication User Authorization Forwarding the user to the tenant application / tenant pages in the SaaS App This demands that the SaaS provider authentication gateway be a scalable microservice that can take care of the load across all tenants. The database partitioning (horizontal or other means) is left upto the SaaS provider Service. Scenario 2 - Global Tenant Identification and User Authentication forwarding   In the above scenario, the tenant identification happens on part of the SaaS provider Tenant Identification gateway. Post which, the