Hacker News Reader

Comment by ablekh | Hacker News Reader

I would not consider this project a proper SaaS boilerplate. It is a Web application boilerplate and maybe a good one, but not SaaS.

SaaS implies multi-tenancy and your project does not seem to offer support for that.

Irrespective to that, your book's regular price IMO is too high - similar books/tutorials/courses (targeting various stacks) can be found for as low as $59.

View on HN

I'm not OP, but it's boldly indicated that the book will be kept up to date and it will be up to the author to continuously provide new content on breaking changes or whatever happens to this stack in the future. $99 seems appropriate to me

A promise to keep a project up-to-date does not imply a promise to add a significant feature, such as multi-tenancy support (assuming that it's missing, that is). Re: price - $99 is pre-order price; by "regular" I referred to post-pre-order price of $199.

SaaS just implies someone else hosts the software. Multi tenancy is one architecture you can use for a SaaS application.

In theory, you're right. However, in practice, SaaS pretty much always implies multi-tenancy. Why would one want to host software for someone else who is a single entity?

Many large enterprise customers want complete segmentation between them and other customers. It is not uncommon for critical apps to not actually be multi tenant but a single deployment.

When you talk about consumer apps or low cost business apps your point is well taken.

edit: Sometimes SSO ties it together so single tenants appear to be a multi tenant environment.

Thank you for clarification. Point taken. Nevertheless, I still stand by my opinion, as multi-tenancy is a fundamental SaaS feature for overwhelming majority of deployment scenarios, both B2B and B2B (where multi-tenant B2B SaaS includes most, if not all, of large and very large enterprise solutions, as well, like Salesforce and SAP). What you are talking about in the first paragraph above is essentially a very specific case of SaaS private deployments. I'm talking about a general de facto standard in the industry.

Thanks for your comment. The `Team` data model is per Team Leader and not visible to other customers. `Team` "contains" `Discussion` and `Post` data models. So same application on the same hardware serves multiple customers. Is this what you call multi-tenancy?

You're welcome. If your boilerplate application allows serving totally independent customers / organizations (not different teams of the same organization!), then, your project is, indeed, multi-tenant and SaaS-compatible. If so, please accept my apologies for missing that aspect of your boilerplate (I looked at it very briefly). Otherwise, my point still stands.

No problem. Thanks.

Reply on news.ycombinator.com