Today we released a scheduled update for the Apigee API Platform, which gives free open access to the same enterprise-grade API Platform used by industry leaders like Walgreens, eBay and AT&T.
This update delivers the following new features and improvements: ability to understand your API traffic by location, approve keys for apps either automatically or manually, get performance metrics by API resource, a 200% improvement in OAuth performance, and more.
Thanks to all who participated in last week's Webcast, "Skeuomorphs, Databases & Mobile Performance," in which @sramji discussed applying the lessons learned from previous eras' computing models to build better end-user experiences and architect for performance on today's mobile devices.
The video and slides for the session are below. We'd love to continue the discussion on the api-craft forum.
Mobile application patterns are different from web application patterns. There are a consistent, discrete set of differences in how they access cloud services. There are consistent reasons why they’re favored over websites as well, primarily based on implicit intent and purposive computing experience, but that’s a subject for a future blog entry.
For now, let’s assume that like web applications, mobile applications use HTTP to access their services, but unlike old-school web applications, they use REST and SOAP as the basis of their service protocols.
Difference 1: Bandwidth is expensive
Bandwidth always costs two...
In enterprise computing, scale has traditionally meant “lots of transactions per second." On Wall Street for many years, “20,000 TPS” was the magic number as it was the rate of a typical market data feed. Infrastructure like TIBCO’s UDP-based information bus and then IBM’s MQSeries became the base platforms for much of this scale of computing, and are still heavily used alongside modern JMS and MSMQ implementations.
Relatively little attention was paid to concurrent connections. Enterprise environments tend to be well-regulated, and most applications will have...
Apigee isn't only for API providers - if you use APIs in your mashup, mobile, or social app you can monitor those APIs as well.
For example, if you're an iPhone developer you know nobody will use a slow iPhone app.
Shorepoint systems is one iPhone shop using Apigee for this purpose on their iPhone apps....
(Following from Tuesday's blog entry on API Scalability and Caching.
Last time we wrote about 3 things to think about when planning how to scale your API.
- Rate limiting and threat protection
- Offloading expensive processing
and then talked about caching at length, so let's finish up with:
Rate Limiting and Threat Protection
Another aspect of scaling is just keeping unnecessary traffic away from your application servers and databases. Some of the techniques that we've discussed previously, such as rate limits and threat protection, apply here...