There has been significant buzz around microservices lately, enough to generate some hype. After implementing heavy and cumbersome SOA solutions for more than a decade, are microservices the solution the industry has been waiting for? Or, are microservices simpler than monolithic solutions?
Microsoft recently announced the initial release of the OneNote API, which enables programmatic integration of its free-form information gathering and multi-user collaboration tool across different programming languages and platforms like Windows, Windows Phone, iOS, Mac OS, Android and the web.
During Build 2014, Microsoft renewed its commitment to the long ignored .NET Micro Framework. This very lightweight version of .NET can be found in for very small devices such as the open source electronics platform Netduino. But the .NET Micro is rather limited, even basic functionality such as accessing REST based resources requires help from people like Daniel Stegmaier of the mfRCF project.
Espresso Logic has added RESTful endpoints for SQL stored procedures to their DBaaS service.
Recently, Marvel has made available a public API and a RESTful service which provides access to their comics metadata.
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.
MuleSoft has just announced the release of three RAML-based tools for designing, evaluating and testing RESTful APIs.
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.
The recently released Webix 1.1 includes improved server side integration and bug detection including the ability to disable any view. It also includes support for REST API and enable developers to define XSS safe template in addition to load data from server side.
In a presentation at the GOTO Berlin Conference Ben Barnard and Felix Leipold, both developers at Nokia in Berlin, shared their experience designing and building a public web API, among other things how to work with an API, that inherently doesn’t have a natural user interface, and challenges in testing for backward compatibility.