ASP.NET Website: Hosting Approach pros & cons

Hello Folks,

I've an application (in ASP.NET) which will be having multi-tenanted feature.

I  would like to have your suggestions/concerns along with pros & cons for website hosting with below approaches.

1.      One website hosting for all customers.
2.      Per customer website.
3.      Hybrid approach i.e. bunch of customers will use one website instance. For e.g. we have 1000 customers and we can make bunch of 10 customers.

Just FYI, we can have one database or separate database(s). We can do customization at back end.

Best Regards,
Mohit Pandit
LVL 5
MohitPanditAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Randy DownsOWNERCommented:
Maybe this article will help.  They started out with separate databases and regretted it down the line.



Considerations for a centralised database:

    Global product SKUs
    Simplified inventory requisitions
    Easier to backup
    Deploy once instead of for every branch

Considerations against a centralised database:

    Easier to differentiate branch requirements with separate DBs
    Modular deployment (one downed branch doesn't break all)
    Harder to manage and develop for shared DB
    I have to re-design invoice numbering (sequence generated by seed)
    Less WHERE clauses everywhere
    Restoring one broken branch has plenty of implications for other branches
0
gheistCommented:
You will need entire server to host many websites.
One site per customer is ok. Just that you need little more memory to hold copy of ASPX per user.
I'd prefer to isolate customers using separate DBs, so that some quick SQL does not expose them to eachother.
Pay attention to SQL connection pooling (DB connections are slow to set up and lot of RAM server side, say 16MB for very starter)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MohitPanditAuthor Commented:
I'll work on it and will share my points as well.
0
MohitPanditAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.