Arnon Rotem-Gal-Oz has written an article following on from other discussions around the term Microservices and whether and how it relates to SOA. According to Arnon, this could be a slippery slope towards the Nonoservices anti-pattern, especially as some people define a Microservice in terms of lines of code.
Using size for defining microservices is useless when determining a service responsibility, Jeppe Cramon states in a series of blog posts explaining his view on microservices and the coupling problems he finds in synchronous two-way communication.
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.
Cloudera recently released the latest version of its software distribution, CDH5. Almost 20 months after the last major version, CDH4 seems like ages in the Big Data world. We take a look at new features this release brings and the future direction of Cloudera after the latest round of investment from Intel and Google Ventures.
We should build systems more loosely coupled to achieve properties like robustness, resilience and scalability, Udi Dahan emphasizes in a recent presentation discussing how we can model our systems using more event-driven and asynchronous patterns and some of the challenges developers face when introducing these principles and patterns into development.
Over the past year or so we've started to hear about Microservices as potentially new architectural style. Recently Thoughtworks' Martin Fowler and James Lewis wrote an article defining Microservices. However, Steve Jones takes issue with the general theme and much in that article, believing that there is little new here and this is just a Service Oriented Deliver approach.
Espresso Logic has added RESTful endpoints for SQL stored procedures to their DBaaS service.
Google have announced general availability of their Cloud SQL service. At launch the service comes with automatic encryption of customer data, a 99.95% uptime SLA and support for databases up to 500GB in size.
Recently, Marvel has made available a public API and a RESTful service which provides access to their comics metadata.
Effektif is launching version 1 of its cloud-based BPM product today. Effektif was started and is lead by Tom Baeyens, the original creator of JBoss' jBPM (acquired by Red Hat) and Activiti, owned by Alfresco. It was set up in partnership with Signavio who invested €1.2m to accelerate development, and who will also be selling the product using their existing channels.
In December 2013, Intel announced its plans to push its latest Intel XDK NEW to the mainstream by making it the official Intel XDK version and inviting all developers to migrate from the previous one by the end of February 2014. Let's look at what Intel XDK is and what is new in its latest release.
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.