Espresso Logic has added RESTful endpoints for SQL stored procedures to their DBaaS service.
Layer 7 recently released the results of a survey focussed on API design and deployment. The survey showed that API designers are divided on security versus usability as their top priority, there is an even split between XML and JSON representations and strong growth is predicted for Hypermedia style APIs. In summary the survey showed there is no one-size-fits-all way to manage APIs.
Amazon has released a new API, the AppStream API, which allows you to programmatically manage apps hosted on the Amazon AppStream platform. For this API, they chose to build it with the HAL media type. HAL is a minimalist hypermedia enabled media type for building machine-to-machine APIs. Amazon is one of the largest organizations to choose hypermedia as a technique for a public-facing product.
MuleSoft recently released a significant upgrade to their Anypoint platform for APIs which brings together API design, collaboration and API management features. InfoQ interviewed MuleSoft CTO, Uri Sarid to find out more about the platform.
Hazelcast, an open source in-memory data grid solution introduces a MapReduce API for its offering.
Recently, Marvel has made available a public API and a RESTful service which provides access to their comics metadata.
The W3C RDF Working Group has moved the JSON-LD and JSON-LD 1.0 Processing Algorithms and API standards forward to recommended status. JSON-LD is a standard to add "linked data" semantics to JSON.
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.