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.
A trend is emerging in which businesses are deprecating ETL (Extract, Transform and Load) - based integrations and replacing them with APIs.
What are the drivers? Why are leading enterprises making this shift for their data?
There’s a fundamental shift in the qualitative nature of today’s data and an explosion of new sources.
Traditionally data was controlled within the enterprise – all of the data that an enterprise gathered were collected when partners and customers interacted with a small number of internal systems. However, in the new apps-based economy, in addition to the systems of record, there are new...
The shift to mobile makes it necessary for enterprises to change the way they engage their customers – we see this all the time with new consumer services such as Uber and Exec disrupting older models. So the imperative and opportunity is to enable enterprises to reach their customers through new types of mobile apps. Trigger.io allows enterprises to reuse their existing web skills and investments to create native mobile apps while Apigee provides a “backend-as-service” solution. This blog post describes how we recently created a native iOS app with a remote data store without ever provisioning a server or writing a line of Objective-C!
Thanks to all who participated in last week's Webcast, "Applying Universal Design Principles to API Initiatives" in which Kevin Swiber (@kevingswiber) and Alan Languirand (@13protons) discussed applying universal and proven design principles and best practices to your entire API initiative. The video and slides for the session are below.
Mainstream culture and subculture have a give-and-take relationship. Strong opinions are formed on both sides as cultural ideas shift between the underground and the commonplace. Let's explore this as it pertains to Web APIs. In the world of Web APIs, a subculture of smart, passionate people formed around REST. While some have different opinions, their approaches share similarities. REST is not a standard; it's a style. As a result of this and a spike in popularity, a branch of REST has emerged. This "pop REST" style is a fusion of traditional REST and alternative techniques.
Software-defined networking (SDN) is changing the economics of large-scale datacenters. Similar to the effect of Linux on the operating system market, OpenFlow is driving disruptive commoditization of expensive network switches, routers, and controllers. As networking shifts to software control, the entire stack of compute, storage and networking now becomes a software-defined datacenter. Where is the software that defines the network? It resides anywhere it needs to, and it uses APIs to read the state of the network and to change the network’s behavior in tandem with changes in application workloads.
Twitter is dropping XML. They recently announced that by March 5th, 2013 their API will no longer support XML as a data format - API v1.1 will support JSON only. What’s the big deal?
It means that every app powered by the Twitter API with XML will break.
Despite the growing popularity of JSON, many developers prefer XML. They are familiar with the parsing libraries, the schema and a powerful collection of XML tools. But after Twitter drops XML, apps built on the XML API will start to see HTTP error responses instead of XML responses. Something like:...