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.
A prototype of MySQL 5.7 is shipping with an optional component called the MySQL HTTP Plugin. This plugin allows direct access to MySQL via a REST over HTTP interface, eliminating the need for a middle-tier server or database specific drivers.
Using microservices is one way of breaking up a monolithic application to gain increased decoupling, separation of concerns and fast deployment but it’s not the only or even the best way, Todd Hoff states comparing the two architectural approaches.
Recently several articles have been written which wonder whether microservices offers a better way of architecting systems or represents a potential problem waiting to happen: distributed Big Balls of Mud. Simon Brown and Gene Hughson discuss the possibility that until people can write well architected monolithic systems they're unlikely to benefit from microservices.
Jeff Lindsay, creator of Dokku and early Docker contributor, discussed in an interview by CenturyLink the Docker related projects he is working on, and how they aim to solve the problems involved in a next generation Docker-based service oriented architecture.
Udi Dahan describes how we in a Service-Oriented Architecture (SOA) where client-side components for one service runs in the same process as components for other services can collect several logical calls into one larger physical call to avoid the high cost, in terms of client to server communication, that otherwise could be substantial.
To take full advantage of the benefits of hypermedia driven systems, the client must allow the server to take the lead and drive the state of the client, Darrel Miller writes comparing with a couple who can dance, one leads and the other just follows, there is no a choreographed sequence of steps defined beforehand.
It's one thing to build a microservices application from scratch, quite another to refactor the architecture of a running application. Karma is doing exactly that and finding benefits and challenges of microservices architecture as they go.
Development and collaboration software vendor Atlassian held its annual developer conference AtlasCamp in Berlin, focusing on the recently launched Atlassian Connect 1.0, the new REST APIs for Confluence and HipChat as well as the JIRA and Confluence Data Center offerings for high availability and performance at scale.
At the Bacon Conference last May, bitly Lead Application Developer Sean O'Connor explained the most relevant lessons bitly developers learned while building a distributed system that handles 6 billions clicks per month.
Managing micro-services means looking after lots of small systems talking to each other and automated provisioning as well as infrastructure automation is crucial, James Lewis states when sharing techniques and practices that have helped him manage the increased operational complexity a microservice architecture gives.
Silk has recently open-sourced a REST framework for Haskell, called "rest". It provides a DSL for defining REST services which can then be run in popular web frameworks such as happstack. This comes with features such as type-safe URLs, abstraction of format-type support, and a clean separation of API specification and business logic.
“I coined the term µServices four years ago defining them as services that always communicate within the same process, without any overhead, as a way to separate these lightweight services from the heavy, costly, and complex services people tended to think about because of the advent of Service Oriented Architectures (SOA)” Peter Kriens recently claimed.