Tag Archives: enterprise architecture

If Your Enterprise Architect Cannot Draw Your Core Architecture From Memory, What Are They?

Enterprise architecture is not the maintenance of modelling tools or diagram repositories; it is the cognitive ownership of structural intent. An enterprise architect must be able to articulate, from memory, the organisation’s core domains, identity flows, state ownership, and integration topology. When architecture lives primarily in tools rather than in the architect’s internal model, complexity is documented rather than reduced, and structural drift becomes institutionalised.

Continue reading

Re-Legacy: The Debt of Deferred Structure

Cloud migration often preserves rather than eliminates legacy when structural redesign is deferred. Re-legacy occurs when outdated domain boundaries, embedded behavioural coupling, and implicit integrations are rehosted under modern infrastructure abstractions. This compounds structural debt, financialises complexity, and stabilises fragility under the banner of transformation. True modernisation requires deliberate structural intervention (redefining boundaries, clarifying state ownership, and reducing coupling) not merely upgrading the substrate.

Continue reading

Data Is a Symptom of Function: Migrating RDBMS Estates Is Not Transformation

Migrating legacy RDBMS estates to the cloud is often framed as a transformation, but relocating data rarely modernises systems. Data is a symptom of underlying business function, encoded behaviour, and dense integration. Without upstream redesign (defining capabilities, decomposing behaviour, clarifying boundaries, and extracting embedded logic) cloud migration preserves complexity, creating “re-legacy” at scale rather than true modernisation.

Continue reading

C# and the Theology of Enterprise Suffering

C# and Azure aren’t just tools; they’re institutional gravity wells. This essay examines how enterprise procurement psychology, stack complexity, and economic capture patterns shape developer culture, delivery speed, and technical decision-making. The question isn’t whether C# works. It’s whether it optimises for craft or for compliance.

Continue reading

What It Means To Be A Business/Technology Architect In A Post Agile, Post AI World

What does it mean to be an architect in a post-agile, post-AI enterprise? This article explores architecture as sense-making, navigation, and organisational memory rather than artefact production. It examines the evolving role of domain and enterprise architects, the value they bring to fast-moving change programmes, and how good architecture enables speed without fragility by preserving coherence, optionality, and shared understanding over time.

Continue reading

From Writes to Reads: Applying CQRS Thinking to Regulated Data Platforms

In regulated financial environments, data duplication is often treated as a failure rather than a necessity. Command Query Responsibility Segregation (CQRS) is an approach to separate concerns such as reads versus writes. This article reframes duplication through CQRS-style thinking, arguing that separating write models (which execute actions) from read models (which explain outcomes) is essential for both safe operation and regulatory defensibility. By making authority explicit and accepting eventual consistency, institutions can act in real time while reconstructing explainable, auditable belief over time. CQRS is presented not as a framework, but as a mental model for survivable data platforms.

Continue reading

Edge Systems Are a Feature: Why OLTP, CRM, and Low-Latency Stores Must Exist

Modern data platforms often treat operational systems as legacy constraints to be eliminated. This article argues the opposite. Transactional systems, CRM platforms, and low-latency decision stores exist because some decisions must be made synchronously, locally, and with authority. These “edge systems” are not architectural debt but purpose-built domains of control. A mature data platform does not replace them or centralise authority falsely; it integrates with them honestly, preserving their decisions, context, and evolution over time.

Continue reading

Azure Data Factory: Why Can’t You Just Do the Simple Thing?

Azure Data Factory can route traffic through a corporate firewall with a fixed outbound IP… but only after you abandon the idea of “simple”. This article explores why a basic enterprise requirement turns into architectural theatre, and what that says about modern cloud platforms.

Continue reading

My Years at Sun Microsystems: From Dream Job to Oracle Redundancy

A memoir of nine years at Sun Microsystems, from the revelation of “The Network is the Computer” and parachuting into nasty projects, to the culture of contrarianism, the pressures of leadership, press training in Nice, and the slow decline into redundancies that culminated with Oracle’s takeover. It closes with reflections on philosophy, craft, people, and the enduring value of diversity and neurodiversity in engineering.

Continue reading