InfoQ Homepage Enterprise Architecture Content on InfoQ
-
/articles/book-review-technology-takers/en/smallimage/qa-technology-takers-logo-1571217600197.jpg)
Q&A on the Book: The Technology Takers – Leading Change in the Digital Era
The Technology Takers – Leading Change in the Digital Era by Jens P. Flanding, Genevieve M. Grabman, and Sheila Q. Cox explains how organizations can achieve competitive advantage through their speed and flexibility in adopting technology. It prescribes a change management approach for adapting workplace behaviors to market-dominating technology to maximize its benefits.
-
/articles/slos-engineering-team-API/en/smallimage/slos-engineering-team-API-s-1571383985025.jpg)
SLOs Are the API for Your Engineering Team
SLOs provide a simple common language for evaluating risk in terms of error budgets. SLOs save everyone involved both time and energy, which you can redirect toward more important things, like keeping your customers happy.
-
/articles/book-review-impact/en/smallimage/paul-gibbons-qa-impact-s-1570434372971.jpg)
Q&A on the Book Impact: 21st Century Change Management, Behavioral Science, and the Future of Work
The book Impact by Paul Gibbons explores how to lead and manage change in the 21st century to support digital transformations while taking the needs of millennials and Gen Z into account. It describes how we can humanize change and use pull models and dialogs to support behavior change.
-
/articles/book-review-managing-technical-debt/en/smallimage/Managing-technical-debt-logo-1569408320780.jpg)
Q&A on the Book Managing Technical Debt
The book Managing Technical Debt by Philippe Kruchten, Robert Nord, and Ipek Ozkaya provides principles and practices that help you gain control of technical debt throughout the software development process and life of the software product.
-
/articles/book-review-engineering-digital-transformation/en/smallimage/engineering-the-digital-transformation-logo-1569308044651.jpg)
Q&A on the Book Engineering the Digital Transformation
The book Engineering the Digital Transformation by Gary Gruver provides a systematic approach for doing continuous improvement in organizations. He explores how we can leverage and modify engineering and manufacturing practices to address the unique characteristics and capabilities of software development.
-
/articles/magic-customer-journeys/en/smallimage/magic-organizing-logo-1568628069360.jpg)
The Magic of Organizing around Customer Journeys - and How to do it
Organizing around the value delivered to the customer requires maturity in the organization that needs to be built up over time. This article describes eight typical steps that companies are taking in order to mature towards the end goal of becoming a true enterprise agile organization, and explains how to move up the ladder.
-
/articles/waste-not-want-not/en/smallimage/waste-not-want-not-s-1562257732956.jpeg)
Waste Not, Want Not: A Simplified Value Stream Map for Uncovering Waste
This article describes a simplified form of Value Stream Maps that makes it easy to visualize bottlenecks and inefficient processes in the software delivery lifecycle. It focuses on the two forms of Lean waste defined as Inventory and Waiting.
-
/articles/developers-business-communicate/en/smallimage/logo-1562065617521.jpg)
How Developers Can Learn the Language of Business Stakeholders
This article explores how business stakeholders and developers can improve their collaboration and communication by learning each other's language and dictionaries. It explores areas where there can be the most tension: talking about impediments and blockers, individual and team learning, real options, and risk management.
-
/articles/obscuring-complexity/en/smallimage/obscuring-complexity-s-1560786483000.jpeg)
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.
-
/articles/cloud-transactions-dahan/en/smallimage/cloud-transactions-dahan-s-1559898649885.jpeg)
How Do We Think about Transactions in (Cloud) Messaging Systems? An Interview with Udi Dahan.
Do today's cloud-based messaging services have different transactional support than those that preceded it? If so, what are the implications? In this interview with distributed systems expert Udi Dahan, we explores the question.
-
/articles/application-integration-service-mesh/en/smallimage/role-application-integration-cloud-native-microservices-landscape-logo-small-1557478517420.jpg)
Application Integration for Microservices Architectures: A Service Mesh Is Not an ESB
A service mesh is only meant to be used as infrastructure for communication between services, and developers should not be building any business logic inside the service mesh. Other frameworks and libraries can be used to implement cloud native enterprise application integration patterns.
-
/articles/api-gateway-service-mesh-app-modernisation/en/smallimage/api-gateway-service-mesh-app-modernisation-s-1556793369643.jpeg)
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.