Flow Debt is a leading indicator that provides a view of what is happening inside a delivery system; an important metric for improving software development. This article provides an example how a metric like Flow Debt can be used improperly, i.e. out of their domain, or properly, i.e. context aware usage of Flow Debt with an IT operations team.
In this podcast, Wes Reisz, chair of the QCon conferences in San Francisco, London and New York talks to Phil Haack, an Engineering Director at GitHub focused on software pushed mostly to the desktop. He’s shipping software like GitHub Desktop, GitHub Extensions for Visual Studio, and the Atom text editor. Phil joined GitHub in 2011 and is a prominent member of the .Net community.
The Open API Initiative group is evolving what has become the de-facto standard API Description Format to produce a consistent and compatible format for describing APIs, allowing interoperation between tooling, systems, and runtime environments. Tony Tam, creator of the popular Swagger Specification is providing an update on the group activity.
With a focus on the business case for a CQRS architecture, this article covers the core concepts of CQRS, and contrasts them with a common, n-tier architecture.
The book Liftoff, Second Edition provides practices and insights for chartering teams by understanding needs, building trust, and defining how to interact in the team and align with the organization.
Often enterprises assume adopting patterns like ESB help in developing with services. However, hidden challenges with these patterns can present dangers which go unnoticed until the system is live.
The HTTP-RPC open-source Java framework returns results in JSON by default, but can use the CTemplate system to respond with custom markup.
Amel Musić demonstrates how T4 can be used to create a flexible code generator that reduces the amount of time and effort it takes to create RESTful services.
In the book How to Lead a Quest Jason Fox explores what can be done to develop insights for strategic decisions and innovation, and for driving progress and delivering value.
What makes an agile team successful is the way people develop an effective level of interaction. Growing agile means both focusing on culture, and on co-evolution of practices and tools. 2
HTTP-RPC is an open-source framework for creating and accessing cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles. 3
This Virtual Panel focuses on some of the current trends in iPaaS. InfoQ has reached out to thought leaders from MuleSoft, SnapLogic and Microsoft to participate in this dialogue.