Many teams are considering how to deploy middleware as a service instead of deploying multiple, traditional middleware platform silos. For example, team members are interested in potential cost savings and vendor alternatives when offering ESB-as-a-Service across multiple tenants.
The ‘Multi-tenant, shared container PaaS TCO’ white paper describes architecture components required to deliver multi-tenant, shared application platform services, and proposes a cost evaluation tool. The cost evaluation tool compares deployment footprint associated with multi-tenant, shared application container PaaS or single tenant, dedicated container PaaS (i.e. traditional application server deployment in Cloud) across multiple tenant counts and application platform service combinations. The worksheet incorporates application platform license (or subscription) cost, PaaS Management service cost, infrastructure expense, and IT management overhead.
Multi-tenant application platform service instances can host multiple tenants with appropriate resource isolation and deliver a significant cost advantage. The container is purpose-built to overcome context isolation challenges, deployment tooling issues, and resource sharing impediments. Multi-tenant shared container platforms use OSGI class loading, custom security managers, Cloud aware code deployer, tenant-aware administration screens, and tenant-aware load balancing to create a safe, multi-tenant environment while maximizing resource sharing and lowering cost.