In this recent webcast, @landlessness and @kevinswiber discussed the 3-tier architecture of presentation, logic and data which power the mobile web. Behind the logic and presentation layers, the data tier is traditionally driven by relational databases. Today, with rich APIs available for developers to store application data, a traditional RDB is often not used by modern apps. This shift is causing the data tier to undergo a great amount of change and is driving change up through the logic and presentation tiers.
Inside nearly every company is an API Machine, a powerful engine that activates latent business value from enterprise systems and databases by plugging directly into the app economy.
Now is the time for companies to turn on the API machine. So, what's important? How do we learn from and avoid the now obvious mistakes that API pioneers have made in the past? How do we create an API initiative that maximizes impact and relevance? We'll review the key patterns for success: Easy Grab Data Handles, . . .
The web and now the mobile web have been powered by the 3-tier architecture of presentation, logic and data. With a rich set of API-powered data capabilities replacing traditional relational database management servers, the landscape for app developers is evolving to one with a lightweight presentation tier, a new set of mobile development platforms, and APIs.
Mobile apps are transforming the way we all live, work and play – and APIs are the "magic ingredients" in apps.
To underscore the growing significance of apps (and APIs) in our everyday lives, we recently conducted a survey with Harris Interactive of over 2,000 Americans about mobile apps and holiday shopping. The results suggest, not surprisingly, that apps are extremely important to consumers - and to retailers.
82% said there are major benefits to shopping on a mobile device, including conveniently browsing for deals, comparing prices and even secretive shopping. 57% are considering purchasing holiday gifts like books and...
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 working with API teams all over the world, a design pattern we've seen work really well is the API Facade Pattern. We touched on the concept in the Web API Design eBook and then in March of this year we explored the API Facade Design Pattern in a bit more depth in a series of short webcasts. We've created a new eBook with the API Facade material that you can download for your favorite e-reader and will hopefully find useful.
"Cachiness factor" is the degree to which your API design supports the caching of responses. Low cachiness means that a relatively higher than optimal number of requests is forwarded to the back end for retrieving data; a high cachiness factor means that the number of requests serviced through the cache layer is reduced and optimized.
Every time a request is sent to the API provider endpoint, the provider incurs the cost of servicing the request. Investing in a good caching mechanism...