InfoQ Homepage Enterprise Architecture Content on InfoQ
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
The Many Flavors of “Low-Code”
While the low-code hype often tells how "citizen developers" can create enterprise applications without the need to code, these platforms can serve an important role for professional developers.
-
Q&A on the Book What’s Your Digital Business Model
The book What’s Your Digital Business Model, by Peter Weill and Stephanie L. Woerner, explores how companies can reinvent themselves to become successful in the digital economy. It provides a research-based framework, coupled with assessments and examples, for executives to think about how to compete in the digital era and decide what’s needed to migrate towards a digital business model.
-
Monitoring and Managing Workflows across Collaborating Microservices
This article argues that you need to balance orchestration and choreography in a microservices architecture in order to be able to understand, manage and change the system.
-
Q&A on the Book Reinventing Jobs
The book Reinventing Jobs by Ravin Jesuthasan and John W. Boudreau provides a framework to understand and optimize the increasingly rapid evolution of work and automation. The framework explores four steps: deconstruct, optimize, automate, and reconfigure; it can be used to bundle work into jobs and create optimal human-machine combinations.