Multi-tenancy
These days, you cannot be too protective of your data. Unfortunately, with most applications, data from one or more accounts is probably sharing space within your other account data. Traditionally, in order to mitigate the risk of access to unauthorized data, you had two choices: 1) more databases (and more hardware), or 2) custom-code “multi-tenancy” into the application business logic. Neither option is a very cost effective, flexible, or secure solution – but there was no other option. Until now.
Secure, Physical Separation of Data - Guaranteed
OpenEdge 11 makes the development and deployment of multi-tenant applications faster and easier by taking nearly all of the cost-intensive aspects of multi-tenancy and making them transparent to the application provider. With OpenEdge 11, multi-tenancy is made straightforward, not just for the user, but for the application provider as well.
Multi-tenant Tables is patent-pending capability available for OpenEdge that provides true multi-tenancy at the database level to ensure that data is physically – not virtually – separated when stored. Because tenant support is implemented in the database layer, the application no longer has to manage tenancy—simplifying the code and making tenancy completely transparent. As a result, you don’t need to rewrite the application. Instead, using a web-based user interface, implementing and managing mult-tenancy is made simple with a template-based approach that delivers increased developer productivity. And OpenEdge 11 gives you the ability to self-provision tenants for Cloud-based applications.
Multi-tenancy Overview
Carl Olofson, Research Vice President at IDC, provides expert insight into the value of multi-tenancy from a business and technology perspective, and provides an update on the current state of the industry.
![]() What is multi-tenancy? |
![]() Why is multi-tenancy important? |
|
![]() Why is multi-tenancy particularly valuable for ISVs? |
![]() Who should think about multi-tenancy? |
Industry Update
![]() Some database vendors believe that multi-tenancy is BAD – what’s your position? |
![]() How do some of the common industry players address multi-tenancy? |
Technology Update
![]() What is currently considered “state-of-the-art” with respect to multi-tenancy? |
![]() What key capabilities are required for a great multi-tenancy solution? |
Business Value
Service efficiency is still best accomplished by automation, which requires consistency to achieve the following:
- Reduce machine resource requirements
- Reduce operational costs
- Reduce the number of instances
- Require fewer administration staff
- Gain economies of scale
- Become more cost effective
- Make it easy to manage
- Single application with multiple customers
- Multiple divisions within a single company
- Support for subsidiary businesses
- R&D sensitive data storage
- Support regulatory compliance
- Financial records
- Health records
- Government legislation
- Facilitate Cloud-enablement
Reduce costs with simplified development
- Minimal application changes
- No tenant-based customizations for queries or other data access
Deploy new customers faster
- Tenant access to data is transparent, based on identity
- Tenants can be quickly and efficiently added, removed, and managed
Decrease maintenance overhead
- Fewer databases to manage, better resource utilization
- Tenant-based utilities and tools make maintenance tasks easier
Maintain security of tenant data
- Physical separation within database – NOT virtual!
- Tenant authentication required for data access














Twitter
Facebook
YouTube
LinkedIn
Developers Network