InfoQ Homepage Architecture Content on InfoQ
-
Self Contained Systems (SCS): Microservices Done Right
Everybody seems to be building microservices these days. There are many different ways to split a system into microservices, and there appears to be little agreement about what microservices actually are - except for the fact that they can be deployed independently. Self-contained Systems are one approach that has been used by a large number of projects.
-
Q&A with Ash Maurya on Scaling Lean
In the book Scaling Lean, Ash Maurya explores how entrepreneurs can collaborate with stakeholders to establish a business model for a new product or service using Lean Startup principles. It builds on top of his first book, Running Lean, showing how to use experiments, measure business progress, and scale your startup.
-
Always Be Publishing: Continuous Integration & Collaboration in Code Repositories for REST API Docs
API documentation is an often overlooked part of making any API a success. This article explores how to make the documentation part of a continuous integration pipeline keeping it closer to the code itself.
-
Does IT Industry Need Better Namings?
The IT industry borrows terms from other domains, which is a fairly good approach. But we distort their meanings or use terms in inconsistent ways, within IT and also in comparison to other disciplines. This article shares some of these leaky terminologies with examples, explains why this matters and suggests how to deal with inconsistencies and improve the situation.
-
From Alibaba to Apache: RocketMQ’s Past, Present, and Future
Feng Jia and Wang Xiaorui share the core distributed systems principals behind RocketMQ, Alibaba's distributed messaging and data streaming platform now open sourced through the Apache Foundation.
-
Q&A on The Rise and Fall of Software Recipes
Darius Blasband has written a book which challenges the conventional wisdom of software engineering: he protests against the adoption of recipes and standards-based approaches and rails against the status-quo. He calls himself a codeaholic who advocates for careful consideration of the specific context and the use of domain specific languages wherever possible.
-
Key Takeaway Points and Lessons Learned from QCon London 2017
This year was the 11th for QCon London; it was also our largest London event to date. Including our 140 speakers we had 1435 team leads, architects, and project managers attending 112 technical sessions across 18 concurrent editorial tracks and 16 in-depth workshops.
-
Automation and Lean: Scaling up the Lean Value Chain
While lean principles enable us to be effective and innovative everywhere we work, finding automation opportunities across every technology and customer focused processes can unlock bigger potential for repeatedly delivering value to customers. This article shows how Ericsson applied lean principles in IT service delivery for automating manual repetitive tasks to improve quality and efficiency.
-
How to Effectively Collect User Feedback in Mobile Application
This article analyzes a variety of forms of collecting feedback in mobile applications from a number of perspectives, including user experience, development, operations,and cost. It also analyzes in which scenario each form of feedback is more applicable, with the purpose of helping mobile application developers or product managers use the right feedback mechanism and improve their products.
-
How to Sell Refactoring? The Case of Nordea Bank AB
Refactoring is often not a technical challenge. Teams can accurately diagnose inefficient code design. If they have sufficient time and budget at their disposal, they would probably get things done. In this article, we focus on the strategic code refactoring. This distinction was introduced by the BNS IT consultants as part of the method called Natural Course of Refactoring.
-
Roundtable: The Role of Enterprise Architecture in a Cloudy World
Do enterprise architects still matter? Has a cloud-native development model—not to mention a DevOps and SRE approaches to operations—fundamentally changed how we think about enterprise architecture? In this roundtable, we talk to four experienced architects to find the answer.
-
Predictable Agile Delivery: The Executive Challenge
As agile grows-out of its years of self-obsession and teenage petulance into a post-agile state, ‘Predictable Agile Delivery’ feels like a realistic goal that advantages both the business sponsor and their development stakeholders. This article shares some ‘good, bad and ugly’ examples of practices that often work and some that always fail at improving large organizations.