Tag: api

Google Sheets Programming

Massively scalable, Highly secure websites (see Google Authentication API), without needing to know anything about EJB, JMX , JBoss, JDBC or any of the hard won knowledge that us Enterprise Java Developers have built up over the last 7-8 years. I’m exaggerating, but not much. What do you think? Is Enterprise Java dead, or is Web 2 just another boost and a slightly different way of doing things for us Java people?

you’d be surprised how many businesses run on nothing but excel. no more boring ‘inhouse app’ coding

Mashup Stats

gmaps api is used by 51% of mashups

Search API Shutdown

Google is protecting its cash cow (search+advertising) by turning off the direct data pipe to search and requiring that you use their library to mediate. Like it or not, it’s their data after all and they can do what they want with it. What’s ironic is that we just spent God knows how many engineering dollars putting an open protocol head (SOAP) on one of our cash cows (Windows).

pretty good discussion on the google soap api shutdown, with comments from markl: The search results we provide are just as rich, if not richer than whats provided by the SOAP API.

End for open web data APIs?

Google is shutting down its SOAP-based search API. Another victory for REST over WS-*? Nope — Google doesn’t have a REST API to replace it. Instead, something much more important is happening, and it could be that REST, WS-*, and the whole of open web data and mash-ups all end up on the losing side.

a trend to watch. these days search api should use opensearch, imho

Mashup growth

And it’s not at all hard to see the value of providing APIs and opening them up on the Web. I often cite that Amazon’s most profitable products are its open Web services APIs which earned them over $200m in revenue last year alone. Though Amazon’s spending on its very innovative Web services products such as S3 and Mechanical Turk has declined, it’s also due to the fact that they’ve staked out a huge amount of territory and are years ahead of many of their competitors. So right now, the money in mashups is currently providing APIs, not necessarily in building the mashups themselves yet, at least out on the Web. But in the enterprise it may be a very different story as these new lightweight models for building applications primarily via rapid integration offers the potential to fundamentally revolutionize the economics of corporate software development.

nice ‘state of mashups’ article

XML vs CSV

I was struck by the distance between DCStat’s namespace-rich XML formats and the CSV format that web apps like Swivel and Dabble DB want to read and write.

heh

Google APIs for Search, Advertising and Commerce

apparently google has a generic api evangelist. i wonder how effective that is? also, no more soap from google

My talk’s main point is that Google exposes many services using different technologies, SOAP, REST, Ajax, so I see the Google APIs in their current state more as a set of Bridges between users and data and processes than a Platform.

General-purpose intermediation

It ought to be trivial to attach an observer and/or filter to HTTP pipelines. Among other things, it could shovel data into a search engine so that I could instantly recall a remembered transaction by search term, by date, or by site.

stefano’s pipelines coming to HTTP. this enabled jon to reverse engineer a gmail api

API Listing by mashups

gmaps has more mashups than the next 10 combined

Boxely

built by joe hewitt as a better XUL. seems to have a strange license attached, oh well.