One way you can reduce the cost of deploying APIs is by deploying multiple API portals using the same platform. Multi-tenancy, a feature offered in WSO2 API Management version 1.4, allows you to do just that.
The core concept of multi-tenancy is that one instance of a software can handle the needs of multiple clients, or tenants. Data is stored in a shared database, but each tenant has access to its own information. Resources are pooled resulting in a major cost savings.
Introduced by Salesforce.com, multi-tenancy is the fundamental software architecture that clouds use to share IT resources cost-efficiently.
“We have taken a concept that is applied to cloud and SaaS and enabled users to deploy it in their own data centers,” explained Chris Haddad, VP of technical evangelism for WSO2.
WSO2 API Manager 1.4 runs on server hardware or in a virtual environment, such as an Amazon or VMware cloud.
Not every company will need more than one API portal. Multi-tenancy works best for those who want to segment their API portfolio and present a custom view and custom access to different audiences. The benefit comes from not having to deploy additional API gateways, analytics or back-office publishing applications.
In addition, while we most often group API resources by service level, apps and users, WSO2 introduces a fourth layer—the domain. WSO2 now lets you group API resources under domains, so you can craft different Apple or Google Marketplace-like storefronts where developers can easily subscribe to and consume APIs.
The latest release of WSO2 also includes support for generating API documentation on Swagger specification, single sign-on through security access mark-up language (SAML), and extended OAuth support for generating access keys.