Over a million developers have joined DZone.

On Deploying WSO2 ESB as a Service

DZone's Guide to

On Deploying WSO2 ESB as a Service

· Cloud Zone ·
Free Resource

Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.

In today’s business environment, increasing agility and lowering cost is a business imperative.  Forward thinking development teams are deploying shared services (e.g. ESB-as-a-Service) instead of traditional middleware silos.  Our total cost of ownership calculation indicates organizations can save significant software subscription cost, operations management effort, and infrastructure expense when deploying multi-tenant, shared container based application platform middleware services.

Many WSO2 clients run several WSO2 Enterprise Service Bus instances in production today, and we encourage our clients to evaluate how implementing ESBs within a Cloud Platform-as-a-Service environment reduces time to market and decreases ownership cost.

Decrease Ownership Cost

For example, sharing an ESB-as-a-Service platform across eight tenants may reduce your organization’s cost by 66% and half server instance count.  While economies of scale benefits further increase beyond eight tenants, even organizations with only four ESB silos can remain investment neutral while benefiting from Cloud Platform-as-a-Service environment improvements.

Reduce Time to Market and Increase Agility

When offering ESB-as-a-Service, time to market is improved, and agility is increased.  Teams can rapidly provision an ESB tenant space, automatically enforce standard security and management features, quickly upload ESB endpoints and mediation flows, and share a reliable, high availability infrastructure configuration.

The Cloud Platform-as-a-Service environment enables tenant specific personalization with required security, SLA, and management isolation.  Personalization may require loading tenant specific code, configuration files, or data.   Tenant specific resources must be isolated and not shared across tenants.  Cloudy tenant-aware security managers, code deployers, and load balancing components built into the WSO2 Stratos Platform as a Service (PaaS) environment achieves expected context separation and resource isolation.

We have created resources that describe how you can make the journey from standalone, terrestrial server silos towards shared Cloud middleware services.  I encourage you to review deployment models shared in our ‘Delivering On-Demand, Shared Middleware Services’ webinar, learn how eBay processes over 1 Billion transactions per day, and evaluate the total cost of ownership advantage when choosing WSO2 Stratos, the only multi-tenant, shared container Platform as a Service offering available today.

Join us in exploring application and infrastructure changes required for running scalable, observable, and portable apps on Kubernetes.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}