- Open source PaaS offerings look to MBaaS to fulfill their mobile app platform requirements.
- FeedHenry and other MBaaS providers differentiate from MEAPs by shifting the focus from the building of the app to how apps connect securely to backend systems.
I have been following PaaS providers’ mobile application platform strategies for the past year and have concluded that leading open source PaaS offerings are opting for MBaaS over traditional MEAP. IBM added the IBM Worklight technology to its PaaS appliance in the spring, and SAP added components of SAP Mobile Platform to the SAP HANA Cloud PaaS platform about the same time. However, the two leading open source enterprise PaaS offerings in this space – VMware/Pivotal Cloud Foundry and Red Hat OpenShift – seem to be pinning all their mobile app platform hopes on a little-known mobile backend-as-a-service (MBaaS) provider called FeedHenry. This is a company worth following, because it has aspirations to continue building out its ecosystem to partner with other leading cloud providers, including those that move in non-middleware circles, such as HP.
FeedHenry may have remained somewhat under the radar, but it has still managed to get the attention of enterprise leaders, including VMware, which lacks the mobile app platform component within its Horizon mobile initiative and has invested in FeedHenry; Red Hat, which has been a huge fan of the company for some time now and plans to leverage its MBaaS to complement its JBoss middleware and PaaS offering; and HP, which may be considering the technology as an enhancement to its HP Cloud. As far as FeedHenry’s go-to-market strategy, it is looking to partner with all these folks and then some, building out its cloud ecosystem beyond Amazon and Rackspace along with its global mobile operator partnerships and even carving out new channel programs to include systems integrators. We will continue to follow and analyze the emerging MBaaS segment of mobile app platforms in coming months through reports and webinars.