Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers, known as tenants. Each tenant's data is isolated and remains invisible to other subscribers, ensuring privacy and security. Tenants can personalize certain components, but do not have access to the core code. Learn more.
Why do companies need a multi-tenant architecture?
Companies need multi-tenant architecture to reduce costs, simplify maintenance, and scale efficiently. Multi-tenancy allows organizations to share infrastructure and data center operations, making it more affordable and easier to manage updates. It is especially beneficial for enterprises managing multiple websites or applications. Read more.
How does multi-tenancy differ from single-tenancy?
In single-tenancy, each customer has their own software instance and may have access to the source code, allowing for greater customization. In multi-tenancy, customers share the same application instance, which is more cost-effective, easier to maintain, and enables larger computing capacity. Updates in multi-tenancy are applied once for all tenants, while single-tenancy requires updates for each instance. Details here.
What is the role of a tenant in multi-tenancy?
A tenant is a customer in a multi-tenant system. Each tenant operates in a shared environment but has isolated data and personalized settings, ensuring privacy and security. More info.
Benefits & Use Cases
What are the main benefits of multi-tenancy?
Multi-tenancy offers lower costs through shared infrastructure, no maintenance fees for updates, ease of configuration, better ROI, and faster maintenance and upgrades. It is ideal for organizations needing federated content and granular user permissions. See benefits.
What are common use cases for multi-tenancy?
Common use cases include SaaS applications, PaaS environments, IaaS services, and any application where multiple clients use the same stack of algorithms. Multi-tenancy is especially useful for enterprises managing multiple websites or digital experiences. Explore use cases.
How does multi-tenancy simplify data access and updates?
Multi-tenancy allows customer data to be more accessible within a single database schema. Updates and releases are streamlined, as vendors only need to update the application once for all tenants, reducing complexity and maintenance costs. Learn more.
Can you share a real-world example of multi-tenancy in action?
Yes. For gamescom 2021, Hygraph was chosen as the multi-tenant headless CMS to manage content from over 200 external exhibitors across 31 countries. Hygraph provided granular permission levels, strong governance, and handled high traffic peaks, enabling secure and efficient content management for all participants. Read the case study.
Hygraph Product Features & Capabilities
What is Hygraph and how does it support multi-tenancy?
Hygraph is a headless CMS with a GraphQL-native architecture that supports multi-tenancy, content federation, and scalability. It enables organizations to manage multiple websites and digital experiences efficiently, with granular permissions and robust governance. See Hygraph features.
What integrations does Hygraph offer?
Hygraph offers integrations with Netlify, Vercel, BigCommerce, commercetools, Shopify, Lokalise, Crowdin, EasyTranslate, Smartling, Aprimo, AWS S3, Bynder, Cloudinary, Mux, Scaleflex Filerobot, Ninetailed, AltText.ai, Adminix, and Plasmic. See all integrations.
Does Hygraph provide an API?
Yes, Hygraph provides a powerful GraphQL API for efficient content fetching and management. API Reference.
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. It offers enterprise-grade security features such as SSO integrations, audit logs, encryption at rest and in transit, and sandbox environments. Security Features.
How does Hygraph perform in terms of content delivery and scalability?
Hygraph is optimized for rapid content delivery, which improves user experience, engagement, and search engine rankings. Its scalable architecture supports high traffic peaks and large-scale digital experiences. Learn more.
What training and support does Hygraph offer?
Hygraph provides 24/7 support via chat, email, and phone. Enterprise customers receive dedicated onboarding and expert guidance. All users have access to documentation, video tutorials, and a community Slack channel. Contact Hygraph.
How easy is it to get started with Hygraph?
Hygraph is designed for ease of use, even for non-technical users. Customers can sign up for a free-forever account and access onboarding guides, documentation, and tutorials. For example, Top Villas launched a new project in just 2 months. Get started.
Pricing & Plans
What is Hygraph's pricing model?
Hygraph offers a free forever Hobby plan, a Growth plan starting at $199/month, and custom Enterprise plans. See pricing details.
Customer Success & Use Cases
Who are some of Hygraph's customers?
Hygraph is trusted by companies such as Sennheiser, HolidayCheck, Ancestry, Samsung, Dr. Oetker, Epic Games, Bandai Namco, Gamescom, Leo Vegas, and Clayton Homes. See case studies.
What industries does Hygraph serve?
Hygraph serves industries including food and beverage, consumer electronics, automotive, healthcare, travel and hospitality, media and publishing, eCommerce, SaaS, marketplace, education technology, and wellness and fitness. Explore industries.
Can you share specific customer success stories?
Yes. Komax achieved 3X faster time to market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement, and Dr. Oetker enhanced their digital experience using MACH architecture. See more success stories.
Pain Points & Solutions
What pain points does Hygraph solve?
Hygraph solves operational pains (reliance on developers, outdated tech stacks, global team conflicts, clunky content creation), financial pains (high costs, slow speed-to-market, expensive maintenance, scalability challenges), and technical pains (boilerplate code, overwhelming queries, evolving schemas, cache problems, OpenID integration challenges). Learn more.
How does Hygraph address these pain points?
Hygraph provides an intuitive interface for non-technical users, modernizes legacy systems with GraphQL-native architecture, ensures consistent branding with content federation, streamlines workflows, reduces operational costs, accelerates speed-to-market, and supports scalability. Technical solutions include simplified development, streamlined query management, and robust security. See solutions.
What KPIs and metrics are associated with Hygraph's solutions?
Key metrics include time saved on content updates, system uptime, speed of deployment, consistency across regions, user satisfaction scores, reduction in operational costs, time to market, maintenance costs, scalability metrics, and performance during peak usage. See KPI details.
Technical Documentation & Resources
Where can I find Hygraph's technical documentation?
Hygraph offers comprehensive technical documentation covering all aspects of building and deploying projects. Access documentation.
Company Vision & Mission
What is Hygraph's vision and mission?
Hygraph's vision is to unify data and enable content federation, empowering businesses to create impactful digital experiences. Its mission is to remove traditional content management pain points through a GraphQL-native architecture, helping organizations modernize their tech stacks and deliver exceptional digital experiences at scale.
Multi-tenancy: What is it and why do you need a multi-tenant architecture?
In this post, we’ll explain the capabilities and benefits of multi-tenant software architecture and why companies should adopt multi-tenant solutions.
Written by Nikola
on Nov 08, 2022
When you think of applications like HubSpot, Salesforce, Zendesk, or Netflix, each subscriber shares the application and has access to a single database.
Such environments are called multi-tenancy.
In this post, we’ll explain the capabilities and benefits of multi-tenant software architecture and why companies should adopt multi-tenant solutions.
Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. In this environment, each customer is called a tenant. In a multi-tenant system, multiple instances of an application operate in a shared environment.
However, each subscriber’s data is isolated and remains invisible to other subscribers. The users can personalize some components of the application, such as the theme colors or notification settings, but they have no access to the core code.
This is made possible because each tenant is integrated physically but logically separated. This means that a single instance of the software can run on one server and can serve multiple tenants.
These tenants can use the same hardware and data storage, creating a dedicated instance for each customer.
SaaS (Software-as-a-Service) or AaaS (Application-as-a-Service) – A complete software solution that organizations purchase on a pay-as-you-go basis from a cloud service provider.
An organization rents the use of an app and allows multiple tenants to connect to it using their respective accounts. All the underlying infrastructure, middleware, app software, and app data are located in the service provider’s data center.
PaaS (Platform-as-a-Service) – A multi-tenancy development environment that users can use to deliver everything from simple cloud-based apps to cloud-enabled enterprise applications. Since the development environment is not hosted locally, developers can work on the application from anywhere in the world.
IaaS (Infrastructure-as-a-Service) – A type of cloud computing service that offers essential computing, storage, and networking resources on demand, on a scalable basis. Each resource is offered as a separate service component, and teams only pay for a particular resource as long as they need it.
For any other application where multiple clients use the same stack of algorithms. The main functionality can be the same or modular and it’s tailored to any of the client’s needs.
Multi-tenancy is in many ways different from single-tenancy, an architecture in which each customer (tenant) has their own software instance and may even get access to source code.
In single-tenant environments, a tenant has a dedicated instance of a SaaS application. This differs from multi-tenancy, where each tenant uses shared services.
Since each tenant occupies a separate environment, they are not bound by the same restrictions as users of shared infrastructure would be.
In other words, single-tenancy architectures are much more customizable.
Still, multi-tenancy is the more used option of the two, as most SaaS runs on multi-tenancy. When compared to single-tenancy, multi-tenancy is cheaper, uses resources more efficiently, costs less to maintain, and enables larger computing capacity.
In the updates department, with a multi-tenant architecture, the provider only has to make updates once. With a single-tenant architecture, the provider needs to address multiple instances of the software in order to make updates.
So why would someone choose single-tenancy over multi-tenancy?
In most cases, it’s because the customer wants to have more control and flexibility in their environment.
Multi-tenancy reduces the purchase cost of applications in two ways:
The economy of scale: Multi-tenancy brings far fewer infrastructure implications than with a single-tenancy solution, as new users get access to the same basic software.
Shared infrastructure: Multi-tenancy SaaS allows companies of all sizes to share the costs of the infrastructure and data center operations. There’s no need to add applications and more hardware to their environment. This way, companies can divert their funds into their core business.
No maintenance fees
When using multi-tenancy solutions, customers don’t need to pay high maintenance fees to keep the software up to date. As vendors roll out new features and updates, those are often included in a SaaS subscription.
Ease of configuration
Thanks to a shared infrastructure, users can configure the environment while leaving the underlying code base unchanged.
In contrast, when single-tenant-hosted solutions need customizing, it requires changes to an application code. These customizations can be costly and make upgrades time-consuming because the upgrade might not be compatible with the environment.
Multi-tenant architecture has a lot of applications in cloud computing. Multi-tenant architectures are used both in a public cloud and a private cloud environment, making sure each tenant’s data is separated from the other.
In a multi-tenant public cloud, for example, the same servers are used in a hosted environment to host multiple users. Each user is given a separate and ideally secure space to store data.
Multi-tenancy can also help providers scale public and private clouds, which has in return, made multi-tenancy a standard. For organizations, multi-tenancy can also provide a better ROI, as well as speed up maintenance and updates.
Multi-tenancy is the ideal architecture to take advantage of cloud servers. More data is migrating from on-premise to the cloud. The 2022 State of Cloud Report reveals that 90% of large enterprises have adopted cloud infrastructure.
By migrating to the cloud, organizations can more efficiently tap into diverse data sources. More specifically, multi-tenancy environments allow businesses to:
Reduce costs – Unlike single-tenant architectures, where each instance of an application needs investment for memory and processing, multi-tenancy allows a large number of applications to share these costs.
Simplify data access – With multi-tenant architecture, the customer data is more accessible. This allows customers to access all data within a single database schema.
Simplify client responsibility – Clients are responsible for software development, such as updates and patches, but not hosting and other areas that are handled within the cloud.
Streamline updates and releases – Multi-tenancy doesn’t require vendors to release data and code to individual client desktops and servers. The packages only need to be installed on a single server.
A real-world multi-tenancy example
Here’s a case study of how an organization chose a headless CMS as a multi-tenant solution for its problem.
Over 200 external exhibitors from 31 countries took part in gamescom 2021 – the largest online gaming convention, setting multiple challenges before the gamescom team.
They had to ensure that all participants were able to match the experience online and have granular permission levels with strong governance, as required by the time-sensitive launch information that gaming companies had to add.
Looking for an ideal solution, the gamescom organizers and partners decided to build a multi-tenancy content platform that would match the performance of a leading streaming platform.
After evaluating several headless CMS, DXP, and custom solutions, the gamescom team chose Hygraph and Frontastic as the perfect tools for what they wanted to achieve.
Thanks to its granular and condition-based permissions, as well as the ability to handle extremely high peaks of traffic and provide a resilient content repository to manage content from over 200 contributors, Hygraph was singled out as a premium solution when paired with a custom frontend for Frontastic.
The teams worked closely with gamescom to set up multiple custom roles for external users with granular permissions.
This way, users were unable to view, edit, or find content from one another, because of the confidential nature of content that was added before the “launch day”.
Multi-tenancy SaaS solutions are designed so that users can configure them to their needs without changing the code structure, which would make the upgrade process difficult.
They are more affordable than single-tenant architecture apps because the processing and storage costs are shared between the tenants.
These features make them especially interesting for organizations that rely on federated content and different user-level permissions.