The NodeJS based Koa web application framework has released version 0.2.0. Koa is the successor of the popular Express MVC platform, but relies heavily on newer ES6 constructs. This release is marked as an important one in that that it reaffirms the team’s design choices from the initial 0.1.0 release, solidifying Koa's API for future releases and production use.
Webix has been updated with support for data-suggest which enables you to make use of images as options. It also adds grid-suggest to select data from a table including support for WebSocket and IndexedDB.
Ole Lensmar, creator of SoapUI, has asked whether REST is really appropriate for architectures that require real-time, asynchronous interactions and binary protocols. In his article he discusses these areas and believes that alternative approaches are required.
The RESTful Web Services Framework Jersey 2.5 was recently released, bringing support for the latest version of Jetty web server, an upgrade of the Apache Connector and numerous defects corrected. Features added in earlier releases, after the major 2.0 release in June, include support for OAuth and Spring 3.
The traditional resource-oriented API model may not satisfy the most important of your API consumers. Daniel Jacobson of Netflix asserts that good API design is about knowing your API consumers and optimizing your API for that audience.
Versioning of services is something which has been a cornerstone problem of SOA. There are many examples over the years of experiences gained and shared, but little in the way of concretely comparing and contrasting different approaches. Jean-Jacques Dubray has written about the experiences of his team in this area and some equations they have developed to try to illustrate the differences.
The recently released List & Label 19 provides support for report parameters, collection variables, new chart types such as combined, stacked, funnel, pipeline, shapefile and donut in addition to support for OData and REST data providers.
Large-scale legacy replacement is the hardest job in the IT industry and REST over HTTP is an attractive option for many of these projects. Architecturally REST has proven scalability and to fit in well with domain modelling, Brandon Byars, a principal consultant at Thoughtworks, claims when sharing his experiences from using RESTful integration in large scale legacy replacement projects.
At the recent Dreamforce event in San Francisco Salesforce launched their Salesforce1 platform. The initial deliverables focus on mobile, and aim to improve on the earlier ‘Touch’ user interface by having a richer set of underlying application programming interfaces (APIs). The launch has been accompanied by new application and admin mobile apps.
API Design and description is more than just a technical interface contract between machines. Apiary's Co-Founder and CEO Jakub Nesetril points out that the real consumer of an API description is the developer, with all the concerns of engagement, usability and communication that entails. We spoke with Jakub recently about Apiary's approach to API design and emerging API tools and workflows.
Apigee Edge now supports Node.js and has open sourced Volos, a project containing a set of API management modules.
Google has released Android 4.4 (KitKat) featuring: lower memory footprint, immersive mode, translucent styles, screen printing, several frameworks – printing, storage, transitions-, Chromium WebView.
MuleSoft has just announced the release of three RAML-based tools for designing, evaluating and testing RESTful APIs.
Using your own public API can be a challenge, Phil Calcado, Director of Engineering at Soundcloud, declared when sharing his experiences managing and rebuilding a large Rails application in a talk at the GOTO Berlin Conference.
Oliver Wolf, a principal consultant, shares his opinionated thoughts about endpoints, domain models, caching, versioning and other matters from the discussions around REST and web APIs taking place in mailing lists and other forums in a talk at the GOTO Berlin Conference.