xPaaS: Making PaaS Enterprise Ready

Red Hat announced xPaaS last year as a rich set of middleware services for building highly complex and sophisticated applications, all working seamlessly together. This is beyond the current state of PaaS where mostly an application container is provided as a service, aka aPaaS (Application Platform as a Service) or ePaas (Enterprise Platform as a a Service). Red Hat envisions xPaaS incorporating integration software to create iPaaS (Integration Platform as a Service), process management and rules management software as bpmPaaS (Business Process Modeling Platform as a Service), mobile capabilities as mPaaS (Mobile Platform as a Service) and MBaas (Mobile Backend as a Service) – all in one unified environment.

xpaas

Red Hat is very well positioned to deliver xPaaS as it can easily leverage the rich portfolio of Red Hat JBoss Middleware and offer these capabilities as services within our public PaaS offering, OpenShift Online, and our private PaaS offering, OpenShift Enterprise. All of these xPaaS services, including aPaaS with JBoss Enterprise Application Platform, iPaaS with JBoss Fuse, bpmPaaS with JBoss BPM technologies and JBoss BRMS, and mobile services with AeroGear, will be provided under a single PaaS environment. Enterprises will not be forced to go to many different PaaS environments in order to obtain what is necessary to build a true, n-tiered enterprise application.

Listen to an overview of xPaaS in this brief video:

xPaaS – making PaaS enterprise ready! Learn all about xPaaS at red.ht/xpaas.

If you are interested in learning more details, DevNation has some great sessions that provide all the details. Here are particular ones that would be interesting:

Sign up for devnation.org today!

 

Be Sociable, Share!

2 thoughts on “xPaaS: Making PaaS Enterprise Ready

  1. IMO, any xPaaS would be named (or identified as a SaaS). Eg when we say esbPaaS it is esb platform as a service, but it is only ESB is serving (not a platform).
    When we have all the aPaaS, iPaaS, bpmPaaS together we can say it is a platform, WDYT?
    Eg see WSO2 PaaS http://wso2.com/cloud/private-paas/ architecture diagram, which is similar to this, there they name the combination of all services as the platform, hence PaaS

Leave a Reply

Your email address will not be published. Required fields are marked *