Multi tenancy with mvc3 and entity framework
Upcoming SlideShare
Loading in...5
×
 

Multi tenancy with mvc3 and entity framework

on

  • 3,381 views

How to implement a Multi-Tenant web application using Asp.net MVC3 and Entity Framework.

How to implement a Multi-Tenant web application using Asp.net MVC3 and Entity Framework.

Statistics

Views

Total Views
3,381
Views on SlideShare
3,370
Embed Views
11

Actions

Likes
3
Downloads
22
Comments
0

4 Embeds 11

http://www.linkedin.com 3
http://www.docseek.net 3
http://www.slashdocs.com 3
http://www.docshut.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Multi tenancy with mvc3 and entity framework Multi tenancy with mvc3 and entity framework Presentation Transcript

  • Multi-tenancy with MVC3 and Entity Framework -By Lasantha Bandara
  • What is a Tenant? Literally“A person who occupies land or propertyrented from a landlord”
  • Is there any better examplethan Exilesoft…?
  • Is there any better examplethan Exilesoft…? Moota
  • Is there any better examplethan Exilesoft…? Moota Pro-Account
  • They are Tenants of Exilesoft… Moota Pro-Account
  • Same situation applies to the cloudbased software applications. In SaaS (Software as a Service) Model Most of the web applications are SaaS – But not Multi-Tenant…! Multi-Tenant Examples,  Highrise  Jira  YaY In these systems, organizations make their accounts and they are provided a look and feel of their own „Home‟
  • Why this is so important? Data is vital for some businesses. Should be able to isolate data among tenants in SaaS model. If we provide it…. We have Competitive Advantage.
  • That implies…Data Architecture is the mostsignificant factor in a MultiTenant Application.
  • We can identify 3 differentarchitectures at present…  Separate DB – Separate Schema  Shared DB – Separate Schema  Shared DB – Shared Schema
  • Separate DB – Separate Schema Extendibilitywith tenant specific requirements Easy Backup High Cost Suitable for Medical and Banking applications in spite of high cost
  • Shared DB – Separate Schema Separate set of tables for each tenant in same DB Extendible and easy to implement Suitable if No. of Tenants < 100 Low cost than the previous one
  • Shared DB – Shared Schema Lowest Cost Additional development effort Less security Each row contains tenant Id Suitable for a huge cluster of tiny tenants
  • Choosing an approach Cost Based
  • Security Shared Isolated
  • Tenant Attributes
  •  Regularity Consideration (legal requirements of companies) Skills set of development team etc…
  •  InYayCRM we have invented a model that is supported all those architectures You can, - distribute databases in a server farm - expand and shrink the number of databases - move tenants among databases
  • Metadata Tenant Database DatabasesClient Application Server
  • Let’s go to demo…