InfoQ Homepage Enterprise Architecture Content on InfoQ
-
/articles/devops-and-cloud-trends-2022/en/smallimage/InfoQ-Trend-Report-logo-small-1648721970880-1655385008093.jpeg)
DevOps and Cloud InfoQ Trends Report – June 2022
This article summarizes how we see the "cloud computing and DevOps" space in 2022, which focuses on fundamental infrastructure and operational patterns, the realization of patterns in technology frameworks, and the design processes and skills that a software architect or engineer must cultivate.
-
/articles/patterns-agility-large-companies/en/smallimage/logo-1648821918548.jpg)
Using Patterns to Drive a Transformation towards Agility - Practical Insights from Large Companies
In the DACH region, a community of transformation leaders from about 30 companies started “DACH30” sessions where they share experiences and insights from their efforts to help their companies become more agile. This article highlights successful patterns to foster change, how to apply flow-oriented design to optimise your delivery capabilities, and the danger of the illusion of control.
-
/articles/mtt-metrics-incident-response/en/smallimage/logo-1647371343575.jpg)
How to Best Use MTT* Metrics to Optimize Your Incident Response
Selecting the correct MTT* metric to improve your incident response is important. If the wrong metric is chosen, the improvements may get lost in the noise of a multivariable equation. This article reviews the various MTT* metrics available and discusses the best scenarios for selecting each one.
-
/articles/continuous-portfolio-management/en/smallimage/logo-1647267787627.jpg)
Continuous Portfolio Management as a Contributor for Achieving Highly-Aligned, Loosely-Coupled Teams
There is a business need for fast software delivery in order to frequently test business hypotheses and drive development based on the resulting feedback. Organizations need to rapidly decide on what to build next, using a short feedback loop that greatly reduces the risk of running on untested assumptions for too long. This article explores a journey towards continuous portfolio management.
-
/articles/Standardized-Specification-Driven-API-Lifecycle/en/smallimage/logo-1647025459155.jpg)
A Standardized, Specification-Driven API Lifecycle
At QCon Plus last November, Kin Lane, Chief Evangelist with Postman, and the Open Technologies Team lead presented on API specifications. API specifications are essential to him and at Postman. So he wanted to share a bit of how they see API specifications impacting how they produce and consume APIs.
-
/articles/ballerina-fullstack-rest-api/en/smallimage/logo-1646298444299.jpg)
Ballerina for Full-Stack Developers: a Guide to Creating Backend APIs
This article explores Ballerina’s intuitive syntax for writing REST APIs. We also discuss authentication, authorization, OpenAPI tool, observability, SQL/NoSQL client libraries, and key language features. At the end of this article, you will have a good understanding of why Ballerina is a prominent candidate for writing your next backend API.
-
/articles/low-code-optimize-time/en/smallimage/logo-1646832000981.jpg)
Low-Code Tools Optimize Engineering Time for Internal Applications
Internal tools are critical pieces of software, often custom-built, and requiring significant developer bandwidth. Low-code platforms can optimize developer productivity, facilitate collaboration, and allow less technical employees to be more active in the development process.
-
/articles/problem-reframing-method/en/smallimage/logo-1646680413270.jpg)
Using the Problem Reframing Method to Build Innovative Solutions
Building products that customers love relies heavily on the problem space: how well you know your audience and how clear are the pain points and main problems your users are facing. This means that the solution to a problem depends on how we frame the problem. This article provides different practices and tools on how to apply problem reframing underpinned by a real case study.
-
/articles/going-digital-pandemic/en/smallimage/logo-1645546134872.jpg)
Going Digital in the Middle of a Pandemic
IBM achieved an enterprise-wide digital transformation program despite the challenges posed by 100% remote work and the pandemic. The article explores various transformation levers such as team set-up, process, architecture, engineering practices & tooling, metrics & governance, and culture, and shows how they were applied to achieve sustainable outcomes.
-
/articles/communicating-engineering-work-business/en/smallimage/logo-1643971643396.jpg)
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
/articles/financial-times-engineering-enablement/en/smallimage/enabling-engineering-productivity-at-the-financial-times-small-1643105626728.jpg)
How the Financial Times Approaches Engineering Enablement
Companies need teams working on infrastructure, tooling and platforms; the way they work has to change so that they do not become a bottleneck. These teams need to be about enabling product teams to deliver business value. Investment in this area pays off as it speeds up many other teams and allows product-team engineers to focus on solving business problems that provide value to the organisation.
-
/articles/avoiding-technical-bankruptcy/en/smallimage/avoiding-technical-bankruptcy-small-image-1640173923994.jpg)
Avoiding Technical Bankruptcy: a Whole-Organization Perspective on Technical Debt
Technical debt is not primarily caused by clumsy programming, and hence we cannot hope to fix it by more skilled programming alone. Rather, technical debt is a third-order effect of poor communication. What we observe and label “technical debt” is the by-product of a dysfunctional process. To fix the problem of accumulating technical debt, we need to fix this broken process.