Leanpub Header

Skip to main content

Topics

Enterprise Architecture

From the architect's role and the frameworks that describe an enterprise to business architecture, services, people and the integration of systems, enterprise architecture as told through the free samples of the Leanpub books about it.

Created from the free samples of 10 Leanpub books and the descriptions and tables of contents of 28 more, with every source cited.

Enterprise architecture is the discipline of describing an organisation as a whole, its business, its information, its systems and its technology, so that a change to any part can be made with an eye to the rest. One writer on this shelf defines it by its neighbours. Business architecture is concerned with the business of the business, process architecture with processes, IT architecture with systems, and others again with buildings and with people and their skills; the role of enterprise architecture is to make sure that all these architectures play well together.[5]

The books here come from two directions. One group is written by architects of large IT organisations and is about the role: what such a person does, for whom, and with what tools. The other is a long series of anthologies from one architect's weblog, which argues for a discipline wider than IT, reaching to values, services and people. Both are wary of the heavy frameworks for which the field is known. One book calls them rigid tools whose output few will take the time to read, while granting that they cover governance, organisation and process, which purely technical methods do not.[2]

This article follows the subject from the architect's role through frameworks and practice, business architecture with value and services, people, story and power, the integration of systems with data and interfaces, and the software architecture and organisational models that border on it. Its sources are the free samples of the Leanpub books listed at the end, with the descriptions and tables of contents of those whose samples were not available or not read, and every claim that rests on a source is cited to it.

Where to start

A newcomer can begin with Creating a career in enterprise-architecture (2022), an anthology of weblog posts on architecture as a career and on how its roles fit together, intended as an introduction,[3] or with 37 Things One Architect Knows About IT Transformation (2024), short episodes from a chief architect's working life.[1] Lean Enterprise Architecture (2026) is a systematic guide whose chapters can be read in any order, and it accompanies a university course.[11]

The experienced developer moving towards the role has Developer to Architect (2026), which begins with the change of mindset the move requires,[12] and The Practical Software Architect (2025), a toolbox with a template for each tool.[2] Better Whiteboard Sketches (2023) is a short book on one everyday skill, the diagram drawn in front of other people.[13]

The practising architect can go by subject: On enterprise-architecture practice for principles and guidance in real projects,[4] Business Architecture Basics for business architecture,[5] and Enterprise Integration Platform (2026) for the connecting of systems.[24] The most advanced of the anthologies are Making Sense of Services in EA (2022), on the modelling of services,[7] and Sensemaking in enterprise architecture, on the frameworks behind frameworks.[15]

History

The idea of an architecture for a whole organisation's information systems dates from the 1980s, when the Zachman Framework, a grid of questions set against points of view, gave the field its first vocabulary. In the 1990s an industry consortium published TOGAF, a method for developing such architectures, and governments began to require them of their agencies; the 2000s added the ArchiMate modelling language and professional certification. Since then the discipline has argued over whether it belongs to the IT department or to the business as a whole.

The books take sides in that argument. The Practical Software Architect notes that the frameworks are described in books that often run past a thousand pages and can be understood only by readers trained in their notation.[2] A weblog post of 2012 collected in On enterprise-architecture practice complains that the full TOGAF certificate was then examined by multiple choice, which tests memory where the work needs experience; its author recalls nearly failing by answering from practice, and concludes that there is no short cut to experience.[4] The same anthology speaks of enterprise architecture breaking out of its old box, in which it was centred on IT.[4] Lean Enterprise Architecture keeps the frameworks and their notations and proposes a lighter way of using them.[11]

The architect's role

37 Things One Architect Knows About IT Transformation defines the role by what it is not. An architect is not a firefighter who runs from one crisis to the next, since architecture needs thought that does not fit between emergencies; not simply the most senior developer, since the two are different careers of equal standing; not a project manager, though managers will lean on one; and not a scientist, since the task is to make complex things easy to understand. Senior architects work at three levels, setting the IT strategy, governing the landscape of systems and delivering projects to stay grounded in reality, and the proposed test of their value is whether the systems still run and can still absorb change after five years. The book's image is a lift in a tall building: in a large organisation those who hold the knowledge are often not those empowered to decide, and the architect rides between the board room and the engine room, carrying technical matters up without losing their essence and business strategy down as technical decisions.[1]

The Practical Software Architect sorts the tools on offer into three kinds and finds each wanting. Architectural patterns and technologies solve technical problems but do not help an organisation to understand the problem it has or to map a way from where it is to where it wants to be. Diagramming methods show a system clearly, the best of them by starting from the high-level view and descending into detail only where it is needed, but they seldom say how the system serves business aims. And the enterprise frameworks produce more material than anyone will read. The author's own toolbox, built up by trial and failure, is in two parts: tools for what the book calls a visible landing, in which a newly arrived architect collects the goals of the business and the needs of stakeholders and plans the evolution of a system from its present state to a target, and tools for spreading the work of architecture through a community instead of keeping it in one office.[2]

Creating a career in enterprise-architecture answers a newcomer's question, how to start enterprise architecture in an organisation that has none. The first requirement is the support of the executives, without which the work goes nowhere, and the way to it is communication: getting them to describe the larger setting in which the organisation operates and the purpose it serves there. The author builds first models from public sources such as the website and the annual report, good enough for people to say that they are wrong, which the book calls a sneaky way of drawing out what they think the models should be. The next priority is allies, because the work depends on personal conversations and on networks inside the organisation that take years to form; one tactic is to sit in the café with interesting diagrams on the table and see who stops. Allies also know the standards that apply, among them the guidelines and workarounds peculiar to the organisation, many of which are written down nowhere. The standard frameworks, on this account, begin to be useful only after all that, and before it can be more hindrance than help.[3] Developer to Architect covers the same passage for the developer, in six parts that run from mindset and technical foundations to decisions, governance and work with stakeholders.[12]

Frameworks and practice

Lean Enterprise Architecture applies one idea throughout: start small, deliver value early and extend the architecture only where the organisation benefits. Its thirty-two chapters in seven parts run from foundations to governance, methods and current technology, and it teaches modelling and communication with the established frameworks and notations by name, among them TOGAF, Zachman and ArchiMate, without the bureaucracy that usually attends them.[11]

On enterprise-architecture practice is the practitioner's counterpart, a collection of principles and of guidance for projects of change. Besides its complaint about certification, the sample contains a characteristic exercise. The four elementary actions on data, to create, read, update and delete, are tried against other kinds of asset, on the ground that an architecture of the whole enterprise must deal with physical things, with relationships between people and with people's attachment to ideas and brands as well as with information.[4] Worked-Examples for EA Practice collects worked cases, with step-by-step checks for routine problems and analyses of architectural errors and their repair.[14]

Three books are about method at one remove. Sensemaking in enterprise architecture offers checklists and models for making sense of a situation and treats the frameworks used to build other frameworks,[15] On Complexity and Enterprise Architecture sets out a frame for mapping complexity and acting on it,[16] and Design Practice Reference (2025) is a reference of design activities and templates gathered from older and newer engineering methods.[17]

Business architecture, value and services

Business Architecture Basics insists that business architecture is one architecture among many and not the centre. Its author warns against two errors, the old one of seeing the enterprise through its IT and the newer one of making the business the sole centre and defining it as everything that is not IT. A business model, in the author's terms, simply is a description of how an organisation is structured to do its business. The sample shows the manner of the series, a weblog post that answers other architects by name and asks to be shown where it is wrong, and it includes a checklist for business transformations whose first items are the story and purpose of the change and its scope, to be mapped not only inside the organisation but through three layers beyond it: those it trades with, the other players in its market, and the governments, communities and investors affected at a distance.[5]

Value, values and effectiveness takes up the word value. A business, it holds, has a relationship of value with every party in its wider enterprise whether or not it says so, and to ignore the unspoken ones is dangerous in the long run; its business model and operating model are derived from its value propositions and the values beneath them, and shareholder value is a derived figure that plays no direct part in the architecture. Within that wider enterprise, which is defined by the values its participants share, a business usually occupies the place of a supplier. A second post objects to the habit of treating a value proposition as a grander name for a product: that is the way of marketing which starts from what a firm can make and then goes looking for a value to attach.[6] Business-models, concepts and frameworks applies the same thinking to the business model and its best-known one-page canvas, including its use outside start-ups and in organisations that do not seek profit.[18]

Making Sense of Services in EA describes everything in an enterprise as a service. Its sample, which follows an invented company throughout, works down through layers of description, from what drives the shared enterprise, which is always larger than the organisation, to lists of what is needed and then to relationships. For the lists the classic questions of what, how, where, who, when and why suffice; for anything deeper the book replaces them with fuller terms, asset, function, location, capability, event and decision. There is deliberately no who among them, since the agent that exercises a capability may be a person, a machine or a piece of software. The author's warning at each step is against letting the model become centred on the business when it should describe the whole enterprise, a mistake that leads to trouble whose cause is then hard to see.[7] User Needs Mapping (2025) approaches the same ground from the needs of the people an organisation serves,[19] and On Economics and Enterprise Architecture sets architecture beside economics and money.[20]

People, story and power

The anthologies return often to what the formal models leave out. On People and Enterprise Architecture distinguishes four kinds of asset: physical things, virtual ones such as data and ideas, relational ones that link people, and aspirational ones that link a person to an idea or a brand. They obey different rules. A physical asset given away is lost to the giver, a virtual one is not, and the last two kinds exist between parties and belong to neither. Most real assets are composites: a book is ideas in a physical object, and money is a number joined to a belief about worth. Many of the muddles of organisational and business architecture, the author argues, come from managing assets that are not physical as though they were, and from thinking in terms of possession where responsibility is the better guide; the example given is the publisher or record company that goes on treating information as a physical object after its product has become data. On this view it is the relationship with a person, not the person, that an architecture should record as an asset.[8]

Three further collections extend the argument: Story and Enterprise Architecture treats story as a framework for architecture in its own right,[21] On power and enterprise architecture examines power and responsibility in organisations,[22] and On futures and Enterprise Architecture the methods used to think about change over long periods.[23]

Integration, data and interfaces

Much of an enterprise architect's concrete work is in the joining of systems that were not built to work together. Enterprise Integration Platform treats the platform that does the joining as a subject in itself, with principles, patterns and their opposites, a method of design, and chapters on security and on the modernising of older middleware.[24] Effective Kafka (2021) is a hands-on guide to building event-driven applications on one widely used streaming platform.[25] On data, Data Mesh Architecture (2023) explains from the engineer's side an approach in which development teams carry out their own analysis of the data they own,[26] and Elements of Data Strategy (2023) sets out the work of planning what an organisation does with its data.[27] Interfaces between organisations are the subject of API Strategy for Open Banking (2020), a collection of articles on the opening of banks' systems to others under regulation,[28] and of Build APIs You Won't Hate: Second Edition (2025), on the design and upkeep of web interfaces.[29]

The foundations beneath have their own strategy books. Cloud Strategy (2024) and Platform Strategy (2026), by the author of the episodes on the architect's role, offer models for decision in place of instructions. The first tells an organisation moving to the cloud to expect a change in its way of life and not one more IT project; the second begins by untangling the overloaded word platform and asking when something deserves the name.[9][10] Modern Applications Strategy (2025) is about choosing which older applications to modernise and how,[30] and Claude Code for Legacy Modernization (2026) about changing critical legacy systems one bounded slice at a time, recovering the business rules hidden in them and building the tests that prove nothing has broken.[31]

Software architecture and the organisation

Several books belong to software architecture proper and are read by enterprise architects for their craft. Coding an Architecture Style (2020) takes one application through layered, hexagonal, modular and microservice styles to show how each appears in code,[32] and Crafting Non-Functional Requirements (2026) goes through the qualities a system must have besides its functions, with the patterns and the pitfalls of each.[33] Better Whiteboard Sketches teaches diagrams that can still be understood after the meeting.[13] How Software Fails (2025) is about failure in complex systems and starts from the position that testing can never guarantee perfection.[34]

Others describe the organisation around the systems. The Cybernetic Enterprise (2025) is an operating model for large organisations in which enterprise architecture, practised leanly, is one group of practices among many,[35] and its companion Foundations of The Cybernetic Enterprise (2025) is a reference to the disciplines on which it draws.[36] The Modern (IT) Organisation (2018) links agile delivery to strategy, budgets and governance.[37] And Human Accountable for The Loop (2026) turns to a new question of governance, proposing eight questions about ownership, delegated authority and limits for any workflow in which AI acts.[38]

Questions about Enterprise Architecture

Which enterprise architecture book should I start with?

A newcomer can begin with Creating a career in enterprise-architecture (2022), an anthology of weblog posts on architecture as a career, intended as an introduction, or with 37 Things One Architect Knows About IT Transformation (2024), short episodes from a chief architect's working life.[3][1] The experienced developer moving towards the role has Developer to Architect (2026), which begins with the change of mindset the move requires.[12]

What is the difference between business architecture and enterprise architecture?

Business architecture is concerned with the business of the business, as process architecture is with processes and IT architecture with systems, and the role of enterprise architecture is to make sure that all these architectures play well together.[5] Business Architecture Basics insists that business architecture is one architecture among many and not the centre.[5]

How do I start enterprise architecture in an organisation that has none?

The first requirement is the support of the executives, without which the work goes nowhere, and the way to it is communication.[3] The author of Creating a career in enterprise-architecture (2022) builds first models from public sources such as the website and the annual report, good enough for people to say that they are wrong, and then looks for allies, because the work depends on personal conversations and on networks that take years to form.[3] The standard frameworks, on this account, begin to be useful only after all that.[3]

Are enterprise architecture frameworks such as TOGAF worth using?

The Practical Software Architect (2025) calls the frameworks rigid tools whose output few will take the time to read, while granting that they cover governance, organisation and process, which purely technical methods do not.[2] Lean Enterprise Architecture (2026) keeps TOGAF, Zachman and ArchiMate and proposes a lighter way of using them: start small, deliver value early and extend the architecture only where the organisation benefits.[11]

Is an architect just the most senior developer?

No. 37 Things One Architect Knows About IT Transformation (2024) holds that the two are different careers of equal standing, and that an architect is not a firefighter, a project manager or a scientist either.[1] Its proposed test of an architect's value is whether the systems still run and can still absorb change after five years.[1]

What counts as an asset in enterprise architecture?

On People and Enterprise Architecture distinguishes four kinds: physical things, virtual ones such as data and ideas, relational ones that link people, and aspirational ones that link a person to an idea or a brand.[8] They obey different rules, since a physical asset given away is lost to the giver and a virtual one is not, and many muddles come, the author argues, from managing assets that are not physical as though they were.[8]

Sources

Every source is a Leanpub book. The note after each says which part of it was read; where no sample was available, only the public description and table of contents were used.

  1. 1.
    37 Things One Architect Knows About IT Transformation, Gregor Hohpe: A Chief Architect's Journey Free sample: the chapters on what architects are and on the architect elevator. 2024. Free sample: PDF · EPUB
  2. 2.
    The Practical Software Architect, Moisés Macero: Hands-on tools and real-life practices to make software architecture work in the real world Free sample: the opening chapter, on the tools available to architects and the plan of the book. 2025. Free sample: PDF
  3. 3.
    Creating a career in enterprise-architecture, Tom Graves: Theory, roles and practice Free sample: a post on starting enterprise architecture in an organisation. 2022. Free sample: PDF · EPUB
  4. 4.
    On enterprise-architecture practice, Tom Graves: Concepts and guidance to underpin practice Free sample: posts on certification and on actions and kinds of asset. Free sample: PDF · EPUB
  5. 5.
    Business Architecture Basics, Tom Graves: Key themes, concepts, practices and guidance Free sample: a post on what business architecture is and the opening of a checklist for transformations. Free sample: PDF · EPUB
  6. 6.
    Value, values and effectiveness, Tom Graves: The underlying core for architectures Free sample: posts on values in architecture and on the value proposition. Free sample: PDF · EPUB
  7. 7.
    Making Sense of Services in EA, Tom Graves: Structure, design, governance and value-flow Free sample: part of a post on layers of description for services. 2022. Free sample: PDF · EPUB
  8. 8.
    On People and Enterprise Architecture, Tom Graves: Tackling people-concerns in architecture-development Free sample: part of a post on services, capabilities and the four kinds of asset. Free sample: PDF · EPUB
  9. 9.
    Cloud Strategy, Gregor Hohpe: A Decision-Based Approach to Successful Cloud Migration Free sample: the introduction and the opening of the first part. 2024. Free sample: PDF · EPUB
  10. 10.
    Platform Strategy, Gregor Hohpe: Innovation Through Harmonization Free sample: the introduction and the opening of the first part. 2026. Free sample: PDF · EPUB
  11. 11.
    Lean Enterprise Architecture, Romano Roth, Dietmar Wettach: A Practical Guide to Value-Driven Enterprise Architecture No sample: from the description and table of contents. 2026.
  12. 12.
    Developer to Architect, Shameel Ahmed Z: Think, Design, and Lead Like a Software Architect From the description and table of contents. 2026. Free sample: PDF · EPUB
  13. 13.
    Better Whiteboard Sketches, Matthew Skelton: How To Sketch Clear Technical Diagrams From the description and table of contents. 2023. Free sample: PDF · EPUB
  14. 14.
    Worked-Examples for EA Practice, Tom Graves: Decision-making in whole-enterprise architecture From the description and table of contents. Free sample: PDF · EPUB
  15. 15.
    Sensemaking in enterprise architecture, Tom Graves: Methods and disciplines for sensemaking No sample: from the description and table of contents.
  16. 16.
    On Complexity and Enterprise Architecture, Tom Graves: Making sense of architecture complexities No sample: from the description and table of contents.
  17. 17.
    Design Practice Reference, Olaf Zimmermann, Mirko Stocker: Activities and Templates to Craft Quality Software in Style No sample: from the description and table of contents. 2025.
  18. 18.
    Business-models, concepts and frameworks, Tom Graves: How to create business-models for all needs No sample: from the description and table of contents.
  19. 19.
    User Needs Mapping, Rich Allen: Aligning Teams Around What Matters No sample: from the description alone. 2025.
  20. 20.
    On Economics and Enterprise Architecture, Tom Graves: How economics and architectures interact From the description and table of contents. Free sample: PDF · EPUB
  21. 21.
    Story and Enterprise Architecture, Tom Graves: Using story to support architecture-development No sample: from the description and table of contents.
  22. 22.
    On power and enterprise architecture, Tom Graves: Exploring how power-issues affect architectures From the description and table of contents. Free sample: PDF · EPUB
  23. 23.
    On futures and Enterprise Architecture, Tom Graves: How to use futures methods in architectures From the description and table of contents. Free sample: PDF · EPUB
  24. 24.
    Enterprise Integration Platform, Sameer Paradkar: Foundations • Principles • Patterns No sample: from the table of contents. 2026.
  25. 25.
    Effective Kafka, Emil Koutanov: A Hands-On Guide to Building Robust and Scalable Event-Driven Applications with Code Examples in Java No sample: from the description and table of contents. 2021.
  26. 26.
    Data Mesh Architecture, Dr. Simon Harrer, Larysa Visengeriyeva, Jochen Christ: From the Engineering Perspective No sample: from the description and table of contents. 2023.
  27. 27.
    Elements of Data Strategy, Boyan Angelov: A Framework for Data and AI-Driven Transformation No sample: from the description and table of contents. 2023.
  28. 28.
    API Strategy for Open Banking, Nordic APIs: Insights and case studies from leading open banking experts and API strategists. From the description and table of contents. 2020. Free sample: PDF · EPUB
  29. 29.
    Build APIs You Won't Hate: Second Edition, Phil Sturgeon: Roughly 80% of the internet is roughly built APIs, held together with enough duct-tape to choke all the hamsters powering it. Let's learn how to build them properly. From the description. 2025. Free sample: PDF · EPUB
  30. 30.
    Modern Applications Strategy, Jaime Nagase: Connecting Business to Architecture Decisions No sample: from the description and table of contents. 2025.
  31. 31.
    Claude Code for Legacy Modernization, Thomas De Vos: Recover Hidden Business Rules, Build a Verification Harness, and Modernize Critical Systems Without Breaking Production No sample: from the description and table of contents. 2026.
  32. 32.
    Coding an Architecture Style, Enrique Pablo Molinari: A practical guide to learn Software Architecture by coding in Java From the description and table of contents. 2020. Free sample: PDF · EPUB
  33. 33.
    Crafting Non-Functional Requirements, Sameer Paradkar: An Illustrated Guide No sample: from the description and table of contents. 2026.
  34. 34.
    How Software Fails, Engin Yöyen: The Hidden Laws of Complex Systems From the description and table of contents. 2025. Free sample: PDF · EPUB
  35. 35.
    The Cybernetic Enterprise, Romano Roth: How to Build a Future-Ready Organization No sample: from the description and table of contents. 2025.
  36. 36.
    Foundations of The Cybernetic Enterprise, Romano Roth: The Bodies of Knowledge Behind Future-Ready Organizations No sample: from the description and table of contents. 2025.
  37. 37.
    The Modern (IT) Organisation, Sandro Quaranta: Be agile from top to bottom From the description and table of contents. 2018. Free sample: PDF
  38. 38.
    Human Accountable for The Loop, Ryan McDonough: How to keep ownership, authority and control when AI acts From the description. 2026. Free sample: PDF · EPUB

Further reading

Other books in the library on neighbouring ground, not cited above.

  • API Product Management, Andrea Zulian, Amancio Bouza: Product Strategy and Execution for the Digital Economy A method for designing, launching and running products offered through programming interfaces. 2021.
  • The Apache Ignite book, Shamim Bhuiyan: The next phase of the distributed systems A hands-on guide to one in-memory distributed database and computing platform. 2025. Free sample: PDF · EPUB
  • Kafka Up and Running for Network DevOps, Eric Chou: Set Your Network Data in Motion An introduction to one event-streaming platform for network engineers. 2021. Free sample: PDF · EPUB
  • AI Transformation, Luca Berton: From AI Pilot to a board-Ready Enterprise Strategy For senior technology leaders: from scattered AI pilots to a roadmap a board can approve. 2026.
  • 10X ORG – Powered by Org Topologies, Alexey Krivitsky, Craig Larman, Roland Flemm: A Manager's Guide to Elevating Business Performance with People and AI A business novel with theory on redesigning an organisation around teams, people and AI. 2026.
  • The Cybernetic Enterprise Assessment, Romano Roth: A Practical Tool for Building Future-Ready Organizations A framework for assessing an organisation's maturity across people, process, technology and data. 2025.
  • The Cybernetic Enterprise CTO Playbook, Romano Roth: A Practical Guide for Building Future-Ready Organizations Rules, plays and a roadmap for technology executives, drawn from a longer operating model. 2025.
  • Observability: Beyond Logs, Metrices and Traces, Sameer Paradkar: Foundations • Principles • Patterns Platforms for observing running systems: foundations, design method and pitfalls. 2026.
  • Designing Trading Systems Volume 1, Code Maverick: Trade Booking, Lifecycle and Flow The main components of a trading system and the flow of trade data between them. 2025.
  • Return Self, Thomas Gordon Lowrey IV: Essays on Recursive Thinking Short essays on recursion in systems, between software architecture and cybernetics. 2025. Free sample: PDF · EPUB
  • Customer Success Management: An ITIL®-Aligned Practice Guide, Natalya Cherepanova Customer success management described as a management practice, with governance, roles and capability levels. 2026. Free sample: PDF

This is an article created from the free samples of 10 Leanpub books and the descriptions and tables of contents of 28 more. We're building these articles to provide you, the Leanpub reader, with a good jumping-off point to discover more Leanpub books that are interesting and relevant to you. We never use material which is paid-only when building these articles: we only use material which is already free on Leanpub. However, Leanpub authors can opt out from inclusion in articles from their book settings page.

Updated November 2026.

In the Leanpub store: 288 books · 1 courses in the Enterprise Architecture category · also filed under Business Architecture, System Integration, Systems Engineering

All topics