Introduction to Multi-Tenant Architecture, Page 4
As an example, say you have a standard multi-tenant designed website that supports the needs for a newspaper company and there are three small newspapers that cannot afford to host their own sites, so they combine their finances to use the multi-tenant solution on a server. They are assigned an IP (999.9.999.9), and then you create host headers that map to the IP:
|IP||Host Header Name||Tenant Id|
(For App URL Table)
Now, when each URL is hit, as demonstrated earlier in the article, you will refer to the App URL to get the proper tenant ID from the URL, thus allowing you to display and load the proper content for the site.
The Multi-Tenant Architecture can be a very powerful design decision when working with potential business solutions that have similar core functionality but differ only in higher-level aspects such as UI and Layout. The concepts explained here are the foundation for the Multi-Tenant Architecture. Depending on your application, there may be extra steps to utilize the design in an effective manner. From my experience, I strongly recommend this architecture when creating platform web solutions where the platform is the core functionality across each application.
About the Author
Neal Schneider (MCTS) is a solutions developer with Crowe Horwath LLP in Indianapolis, Indiana. Neal specializes in Web-Based solutions. Reach him at email@example.com.
Page 4 of 4