In stead of feature farming, we need to deliver better outcomes and focus on the business results that we need to deliver. Measurements should provide insight into the outcomes because that is what is important. The Mobius loop can be used to define appropriate measurements.
After gestating for more than a year on GitHub, the project Streams has now been adopted by WHATWG in an effort to standardize a web streaming API. The project is led by Domenic Denicola, the man that started the work on Promises, currently part of the upcoming ECMAScript 6.
W3C published a new version of the HTML5 Differences from HTML4 working draft. The latest version describes the differences of W3C HTML5 and HTML4, and a comparison between WHATWG HTML and HTML4 is no longer covered.
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.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.
Creating and maintaining a Quality Management System (QMS) can be difficult, certainly when organizations have multiple product lines where different regulations and standards are applicable. InfoQ interviewed Willem van den Biggelaar about the benefits of having a QMS, dealing with multiple regulations, assuring adherence, how a QMS can support agility and deploying a QMS in an agile way.
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.
In agile projects the product owner is often seen as the person who primary assures the connection between business and IT. But for effective IT-Business alignment having a product owner is not enough. What can people from the business, demand and supply parts of the organization do increase the effectiveness of IT – Business alignment?
A group of representatives from Stack Exchange, GitHub, Reddit, and others have started to standardize and enhance Markdown under the name Standard Markdown. Their efforts have met the opposition of John Gruber, the syntax’s creator, who does not want to see Markdown used in other projects, so the project was eventually renamed CommonMark.
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.