Hey everyone,
I'm writing a blog 100% focused on building a multi-tenant SaaS in the tech / developer tooling space.
I post a new post every 7 days (at least). It's all real life, fairly technical stuff: no generic, motivational posts or rehashing of SaaS/Startup tropes.
Blog is at: https://blog.checklyhq.com/
Last post was on enforcing feature limits in a multi-tenant SaaS situation. Before that, I had a deep dive into our basic SaaS data model.
I hope this helps anyone out there. Hit me up if you have any questions.
We have built several multi-tenant SaaS. One that solves a big inherit design flaw with some multi-tenant models. One thing we did is extract feature clusters, in micro services. We felt RESTful services, was faster than db i/o. We believed in keeping the multi-tenant model free from complexity. We re architected in 2018, to solve a shared db model scale problem. There is a great white paper from the go daddy CTO.
Any chance you could provide link or title? Can't seem to find googling it. TIA.
We don't work in Microsoft technologies, but these guys wrote some nice technical articles. https://azure.microsoft.com/en-us/blog/new-multi-tenant-patterns-for-building-saas-applications-on-sql-database/ - Our design uses the catalog database with Postgresql. We can scale to any size. It is well known by those who have at or above 80,000 tenants, the database is the problem. https://docs.microsoft.com/en-us/azure/sql-database/saas-tenancy-welcome-wingtip-tickets-app
Good! Is Checkly multi-tenant?
absolutely!