{"id":434868,"date":"2010-03-16T15:48:19","date_gmt":"2010-03-16T19:48:19","guid":{"rendered":"http:\/\/gigaom.com\/?p=106161"},"modified":"2010-03-16T15:48:19","modified_gmt":"2010-03-16T19:48:19","slug":"sxsw-the-future-application-ecosystem","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/434868","title":{"rendered":"SXSW: The Future Application Ecosystem"},"content":{"rendered":"

\"\"<\/a>In a world of web-based services that depend on various other services, like Twitter or Google Maps data, your product will only be as strong as your weakest API call. I’ve found it’s actually a fun topic to discuss. For developers and web-based businesses, thinking about and managing federated flows of information<\/a> has a big impact on the end-user experience.<\/p>\n

I moderated the Can You Run a Serverless Business <\/a>panel a few hours ago, and two of the panelists brought that up as an issue, with Jim Louderback of Revision3 (an occasional columnist for GigaOM) saying that at one point he ended up slowing down that company’s video delivery because it had relied on too many services located in the cloud, a sentiment echoed by Ethan Kaplan of Warner Music. It’s a topic I discussed yesterday with Sam Ramji, at Sonoa, which offers a service that helps track the health of APIs<\/a>.<\/p>\n

But after surveying the audience at the panel via a show of hands as to what type of different web and cloud services they use, it was clear that most were using a mix of software, platforms and infrastructure as a service, with some also using traditional hosting or running their own data centers. Information technology has always been a confusing mix of gear and services, but it seems like that complexity is only expanding in terms of how and where you can build an offering as well as the “partners” whose APIs you might use to build a product.<\/p>\n