1 / 11

Design Strategy for Data Isolation

Design Strategy for Data Isolation

Diya
Download Presentation

Design Strategy for Data Isolation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Strategy for Data Isolation in SaaS Model

  2. TO BE or NOT TO BE – Isolated? One common question raised while dealing with any SaaS architecture is whether there needs to be an isolated database for every customer or should there be a shared database / shared table for all customers. Tenant A Tenant A Tenant B Tenant B Multi-Tenant Database Tenant C Tenant C www.techcello.com

  3. Decision Parameters To take a decision you should ask the following questions, • Will my customers be willing to share the data with other customers or is it a big no? • Do my customers demand access to the database? • Will my customers need the option to individually backup and restore the data at any point in time? • Is the data volume high for all customers? • Will the workload from all my customers be high and at the same time(concurrency)? www.techcello.com

  4. Inferences • Will my customers be willing to share the data with other customers or is it a big no? www.techcello.com

  5. Inferences • Do my customers demand access to the database? www.techcello.com

  6. Inferences • Will my customers need the option to individually backup and restore the data at any point in time? www.techcello.com

  7. Inferences • Is the data volume high for all customers? • Will the workload from all my customers be high and at the same time(concurrency)? www.techcello.com

  8. Ideal Option In SaaS Expect mixed set of customers with different preferences Go for a hybrid model where you completely design for a shared table approach Have an option to isolate specific customers on a need basis Designing for Sharding by Tenants will allow you to achieve hybrid support www.techcello.com

  9. About TechCello Techcello is a cloud-ready, SaaS Application Development Framework Can be used to, Build new SaaS products Convert single-tenant Apps to Multi-Tenant Migrate on premise products to SaaS model Cello framework is delivered as a set of libraries and APIs that can be easily integrated to your product Applications built using Cello can be deployed in any cloud Cello contains building blocks for developing, monetizing and servicing your SaaS offering. www.techcello.com

  10. TechCello – Flexible Architecture TechCello supports all models of database multi-tenancy, there by allowing ISVs to operate in a hybrid model. TechCello offers an end to end SaaS Life Cycle Management Solution that can help in designing, developing and managing the operations of your SaaS product. TechCello is tested and proven SaaS Framework, built exclusively to meet the typical SaaS needs of your business and product. TechCello offers more than 30+ modules covering all the basic engineering blocks and operational modules. Using TechCello you can simply focus on building your product functionalities, and TechCello can take care of the rest. Apart from saving significant amount of cost, your precious time can be well spent on differentiating your product from competitors through unique product features. www.techcello.com

  11. Contact Us http://www.techcello.com sales@techcello.com www.techcello.com

More Related