Working with a microservices architecture creating small services with a need for light-weight mechanisms, independent deployment, scalability and portability, a container technology like Docker can provide an ideal environment for deployment of these services with respect to speed, isolation management, and lifecycle.
Moving to Continuous Delivery and speeding things up, the rate of change have increased at the same time as the cost, size and risk of change has reduced, an DevOps and agile transformation, and a containerization that is very compelling for businesses of nowadays, Adrian Cockcroft explained in his keynote at the recent Docker conference in Amsterdam.
Restlet has released version 2.3 of its Restlet Framework. This release is largely an effort to update the project's dependencies and to improve its API documentation and management. Restlet has been developing a comprehensive API platform with Restlet Studio (a web IDE for building APIs), APISpark (a PaaS for building API's), as well as Restlet Framework (its open source offering.)
ThoughtWorks has published a digital preview of the January 2015 radar, providing opinion on techniques, tools, platforms and languages and taking a snapshot of the current trends in software technology.
There is a strong trend for microservice based architectures and frequent discussions comparing them to monoliths, Robert Annett explains and defines a monolith as an architectural style or a pattern using three basic viewtypes for characterization.
Mark Nottingham, chair of the HTTP Working Group, asks the question What is the Web? As he mentions, this simple question has some complex and perhaps unexpected answers depending upon your perspective. A common approach would be to say that it has to be rooted in the Web browser, but that has some interesting consequences, not all of which are useful for non-browser stakeholders.
At the StrataHadoop conference in Barcelona last week, Rod Smith, Vice President of the IBM Emerging Internet Technologies organization, presented work on an internal product they have been developing in their consulting work with clients that integrates data sources, and data analysis.
Microservices are not new ideas and we will over the course of 3-5 years end up rebuilding WS-* the same way Web Services did rebuild all from CORBA unless we learn from our mistakes and improve to prevent them from being made again, Greg Young stated in a presentation at the Microservices Conference in London.
Microservices are valuable, but to break things up properly creating the right boundaries we need to understand our business and its processes Jeppe Cramon stated in a presentation at the Microservices Conference in London.
Udi Dahan describes how looking for highly cohesive, loosely coupled microservices, not within a system but over the enterprise, we can end up with a focus on organising services around business capabilities spanning the whole organisation since this is what the business care about.
Chad Fowler, CTO at 6Wunderkinder, the company behind Wunderlist, describes how they went from a large monolithic Rails application and a large monolithic database to a system with many microservices, and the architecture they ended up with. Starting by adding new functionality as services and splitting the large database into smaller databases, they ended up doing a big rewrite of a new system.
Service-Oriented Architecture (SOA) is a very broad term and practically meaningless. Microservices is a subset of SOA with the value being that it allows us to put a label on this useful subset of SOA terminology, Martin Fowler stated in his keynote introducing Microservices when opening the GOTO Berlin Conference 2014.
The Apache Camel team recently released version 2.14, their 66th release. Camel is an open-source integration framework that provides components based on the popular enterprise integration patterns. It allows an application to define route and mediation rules in many domain-specific languages (DSLs), for example with Java, XML, Groovy and Scala.
The second version of the Reactive Manifesto was announced at September's GOTO conference in Aarhus. Martin Thompson discusses the need for a revised version of the Manifesto and what its changes mean for the burgeoning reactive community.
Several companies have reported their move to adopting Microservices. Recently Tom Livesey from startup Droplet has joined the discussions by posting several lessons they learnt when moving to that architectural approach.