the APIstrat experience

More than 300 representatives from research and industry across the globe participated in the Api Conference, Practice and Strategy in Amsterdam held in Beurs van Berlage building on the Damrak, in the centre of Amsterdam.

on March 26th-28th, 2014, co-organized by the leading key players of the API economy.
20140327-untitled-shoot-5474.jpg
Opening remarks by Kin Lane, API Evangelist and Steve Willmott, CEO of 3Scale
There were so many different topics and areas of API practice and research. The main theme logo was “Scaling in the API Economy”. Even though that was the core concept, all aspects regarding APIS were examined. The entire API lifecycle was discussed in detail as well as each part of that separately. Fresh ideas and nice startups were there to discuss their approaches on the boosting API economy.
OPENi is a project focusing on the technologies of the web, and especially whatever has to do with APIs. No matter if those APIs are REST, SOAP, or any other way. The idea is always the same. If a company wants to expose a service for customers to use, this is of the OPENi interest. In OPENi we are trying to build an ecosystem of both cloudlets and cloud based services in a highly correlated manner.
Thanks to the conversations and the presentations held in the conference, new concepts were introduced within the consortium. Instead of API hubs, the more “trendy” term of API node seemed more appropriate for the OPENi terms.
Two extremely interesting presentations from the academic community focusing on API descriptions captured immediately my attention. Markus Lanthaler who was there to present and discuss about the Hydra community group, which is an effort in the road to “simplify the development of interoperable,hypermedia-driven Web APIs”. Hydra is based on top of JSON-LD, utilizing all the nice toolkit provided by RDF and similar technologies. In a quite similar manner, Ruben Verborgh upstretched the issue that hypermedia is not adequate. Since we are migrating a step forward to the future of the web, were API nodes is the new trend for scaling, the current hypermedia description for APIs are not enough. Clients should scale in a manner that could identify changes and comprehend new functionalities on the fly. For that reason, new mechanisms are in need of being conceived.
20140327-untitled-shoot-5556.jpg
Keynote: Romain Huet (@romainhuet), Developer Advocate at Twitter. Keynote:
Connecting to the pulse of the planet. Yes. That is a drone
Many warm thanks to Kin Lane, for inviting us to this nice API celebration and we are definitely looking forward to meeting him again in future such events were we could share a deeper insight on the notions of API descriptions and how such an approach could scale in an enterprise level.


( Pictures were taken from the 3scale Blog)

Σχόλια

Δημοσίευση σχολίου

Δημοφιλείς αναρτήσεις από αυτό το ιστολόγιο

One day at the WS-REST workshop in Florence

Εικόνα
I am really excited to write this article. I indeed had a wonderful time participating both as a presenter as well as an attendee for my first ever  ws-rest  workshop which is collocated each year with the famous WWW conference . The program was full of interesting topics, regarding (what else) discussions about REST practices, research and new ideas. I am borrowing its description here! Web APIs for a Web in evolution The Web is changing at a tremendous speed, and Web APIs play an important part in that. In fact, the number of Web APIs is growing so quickly that we face many challenges. The WS-REST workshop series aim to connect Web researchers and engineers to tackle the issues we are facing. Many of them are not solved by far: How to dynamically integrate Web APIs? How to create intelligent clients for Web APIs? How can we deal with the enormous growth and diversity? Session 1 First, to kick start the session,  Erik Wilde  had the floor for a super interesting k
Read more

PyAPI: A python library to play with various API Standards, like Hydra, Swagger, RAML and more

Εικόνα
Ever been in a situation where your manager asks you to write documentation for the APIs that you developed? Let’s face it, if you’re like most developers, you love to code and hate to write. Furthermore, writing takes time away from critical tasks you need to do, such as feature development and bug fixing. It’s no surprise that API documentation often ends up being frustrating and confusing for the reader—it rarely gets the attention it deserves. Hopefully nowadays there are many nice tools to document your APIs .  Why Document Your APIs? Let’s start with the non-technical side of the issue. API documentation has been around ever since the first programming languages were created. There’s been plenty of time to develop effective processes for creating quality documentation, yet well-written API documentation is still quite rare. Why doesn’t it happen? First, documentation is seldom prioritized. Even though it has a large impact on how much a software platform is adopted,
Read more

What is the Semantic Web?

The Semantic Web is an idea of World Wide Web inventor  Tim Berners-Lee  that the Web as a whole can be made more intelligent and perhaps even intuitive about how to serve a user's needs. Berners-Lee observes that although  search engine s index much of the Web's content, they have little ability to select the pages that a user really wants or needs. He foresees a number of ways in which developers and authors, singly or in collaborations, can use self-descriptions and other techniques so that context-understanding programs can selectively find what users want. Web 2.0 Is Not the Semantic Web Web 2.0 is all about people. It's a social thing. The second generation of the World Wide Web is focused on the ability for people to collaborate and share information online. Where the Web contains static  HTML  pages, Web 2.0 is  dynamic , in that it serves applications to users and offers open communications with an emphasis on Web-based communities. Web 2.0, because it focu
Read more