Apigee makes use of the latest and greatest big data technologies such as Cassandra to power its products. Apigee App Services, which power mobile and rich client applications from the cloud, are based on Usergrid (Apigee's open source data platform built on Cassandra).
In last week's Webcast, Building a Mobile Data Platform with Cassandra - Apigee Under the Hood, @edanuff and @landlessness discussed how Apigee implemented multi-tenancy at scale in Usergrid.
In my previous article, I discussed the emergence of Backend as a Service (BaaS) as a solution for the traditional server side stack. Instead of spending months building a backend, mobile and web app developers can now leverage services to help them deliver higher quality apps in less time than ever before. In this post we look at a few of the common features that a BaaS solution brings to the table. We will also show the API endpoints that developers can use to take advantage of these features in their apps.
What do mobile apps need?
In today's competitive...
Apigee is thrilled to announce the public beta of Usergrid: the easy, API-based way to build out app capabilities.
Usergrid starts with a simple REST API and OAuth layer, and adds elegant routes & resources to let you handle mainstay features for your app such as:
- User sign up & sign in
- Sign in with third-party services like Facebook
- Storage of arbitrary data: if you can write it up or serialize it in JSON, we can store it
- Social graph building & traversal, between users & objects (friendships, followships, likes, etc.)
- Storage & retrieval of activity streams, such as walls, ...
In 1995, Clayton Christenson coined the term Disruptive Innovations in his article titled "Disruptive Technologies: Catching the Wave." His contention was that some new products or services that appear in the marketplace are so revolutionary that they render existing technologies obsolete. We are seeing a new example of this phenomenon with the emergence of a sector being referred to as "Backend as a Service"—BaaS. BaaS is replacing the traditional server-side stack as a dependable, feature-rich option for powering mobile and web apps.
Sidelining the competition
Proponents of existing technologies may initially perceive new innovations to be no more than novelties,...
Time for a quick recap of when and where you'll find us in the coming months. We will be in full force at GlueCon near Denver next week, with two presentations. Ed Anuff, creator of Usergrid, will talk about the perils of designing a massively multiuser app platform (Breakout 2, 1:45pm on Tuesday May 22). Sam Ramji, our VP of Strategy will talk about the balancing act of control & performance in the face of mobile devices and API-powered ecosystems (Breakout 3, 4:50pm on Tuesday May 22).
Thanks to all who participated in the Mobile Apps 101 Webinar last week about "designing apps that people want to use." The video and slides are below.
Check them out for an introduction to some key patterns for mobile app development—repeatable patterns that represent functionality for the front and back-end of mobile apps. Thanks @edanuff, @gbrail, @timanglade.
For years, building web apps has required server-side code and a database. That was great for browsers, but then mobile apps came along and changed everything. Today apps appear on any number of devices, including browsers, and the same app needs to run seamlessly on multiple devices.
Apps are fundamentally different from their web application counterparts. Traditional web applications run on a monolithic, server-side stack, which delivers content in the form of web pages. For the most part, browsers simply display this content. When a user interacts with a web page, requests are sent to the server for additional content....