You have a SaaS app that lets their users upload static files (HTML, CSS, and JS). Now you may support their website URL as domain.com/ted/portfolio.html. This is a good approach, but this doesn't seem good for the user or to share with others. For that, what we can do is to assign a custom subdomain for each user and show the same websites.
ted.domain.com --> domain.com/ted/portfolio.html
This makes the system cleaner and structured in any SaaS application.
The best example of a multi-tenant application you have already used is GitHub
You may have used one in your time. You have uploaded your static files, which may have HTML and CSS, and then from GitHub Pages you made it live and sharable to the internet for everyone. Your page URL might be like "ted.github.com/porfolio." This is a multi-tenant architectured derived system. which lets users get their own personalized subdomain and show the content.
I recently found this concept while debugging for another topic. I have heard of the tip of the iceberg previously somewhere in the IT; now I just learned what it is. It really made me think. How did it work, and can I really make it live or just a concept only? So I researched and found a video, which really guided me to actually build it. Piyush Garg's video just watched. I haven't built it by myself, but I am working on it. Soon drop it in public as well.
0 Comments