{"API Evangelist"}

Overview Of The Backend as a Service (BaaS) Space

Prepared By Kin Lane

May 2013

Table of Contents

  • Backend as a Service
    • What is BaaS?
    • How Does BaaS Differ From IaaS and PaaS?
    • What Are The Benefits of BaaS?
    • What Can You Build With BaaS?
  • Who Are The Top BaaS Providers?
  • What Are The Common Building Blocks of BaaS?
  • What Are the Common Approaches to BaaS Pricing?
  • What Are The Other Approaches to BaaS Pricing?
  • Who Are The Other BaaS Providers?
  • Watch Out As 1000lb Gorillas Set Their Sights on BaaS Space!
  • What Makes BaaS Relevant to APIs?
  • The Future Is About Virtualized Mobile Operating Systems
  • Investment in BaaS
  • What Are The Opportunities in BaaS?
  • Summing Up BaaS
  • Appendix A: Full List of BaaS Features
  • Appendix B: Curated News Sources


Backend as a Service

There is an emerging trend in mobile application development, that people are calling backend as a service (BaaS), also known sometimes known as mobile backend as a service (MBaaS). With the growth in the number of mobile devices like iPhone from Apple, Android from Google, Windows Phones from Microsoft and the historic contender Blackberry, a number of BaaS providers are emerging to meet the demand for building, deploying and managing the mobile app life-cycle.

What is BaaS?

BaaS is an approach for providing web and mobile app developers with a way to connect their applications to backend cloud storage and processing while also providing common features such as user management, push notifications, social networking integration, and other features that mobile users demand from their apps these days.

This new breed of BaaS services are provided via custom software development kits (SDK) and application programming interfaces (APIs). BaaS is a relatively recent development in cloud computing, with most BaaS start-ups dating from 2011 or later. The global BaaS market is estimated to grow from $216.5 million in 2012 to $7.7 billion in 2017 from a report published by MarketsandMarkets.

How Does BaaS Differ From IaaS and PaaS?

Baas has evolved out of frustration around deployment of IaaS platforms like Amazon Web Services, just to fire up a single new mobile application--accompanied with the fact that the traditional PaaS offerings have not stayed on top of what is needed for mobile developers. BaaS is about abstracting away the complexities of launching and managing your own infrastructure, then bridging a stack of meaningful resources targeting exactly what developers need to build the next generation of mobile apps.

BaaS, has a lot of the same intent as PaaS, to speed up the application development process, but BaaS is purely a backend, providing an infrastructure that automatically scales and optimizes, bundled with a set of essential resources developers require, like content, data, messaging tools and all best 3rd party, API driven services they are used to like Facebook, Twitter and Dropbox.  

What Are The Benefits of BaaS?

BaaS is all about making developers lives easier. BaaS is born out of a shortage of mobile developer talent and an overwhelming demand for high quality mobile apps, not just on iOS, but across Android, Windows and Blackberry devices.  

BaaS Delivers:

BaaS tends to reflect what is consider to be a no-ops development environment that allows companies and developers focus just on building the best applications with the most unique feature set.  All of the infrastructure deployment and management that is historically associated with developing applications is abstracted away into a single backend platform.

What Can You Build With BaaS?

While BaaS is primarily focused on mobile application development, the approach has characteristics that can easily be used across multiple areas of development:

What is possible with BaaS varies depending on the platform provider, but we are starting to see some common building blocks emerge from the 40+ BaaS providers on the landscape currently.

BaaS is a natural response to software development being moved into the cloud, and the decoupling of common resources into individual APIs.  In 2013 we know we need our platforms to perform and scale in the cloud, while bringing the resources we depend on into meaningful sets that we can efficiently build apps around, without having to go gather them from around the web.