/ Resources

Enterprise Architecture
the complete series

Ten editions on the architecture patterns enterprise systems are actually built from — what each one buys, what it costs, and the conditions under which it stops paying.

The field guide

The whole run, collected

All ten editions in one document, in series order, with the diagram from each.

Download the PDF

No form, no email address, no gate. The PDF is the same words as the pages below.

Neeraj Kumar

Founder and Principal Architect

MCA · Data Science · 8+ enterprise certifications

Professional profile

Published editions

10 of 10 published so far. Each lands in full on this site on the date shown.

  1. Layered Architecture: Start With Clear BoundariesAugust 27, 2026Architecture gets complicated when boundaries become blurry. Why one of the longest-standing patterns in enterprise software is still one of the most useful — and what goes wrong when its layers become folders rather than decisions.Edition 1 cover: “Layered Architecture — the foundation of structured systems”. A four-box stack runs presentation, business logic, data access and database, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  2. Modular Monolith: Modularity Before DistributionAugust 28, 2026Microservices are not the only way to achieve modularity, and for many systems they are not where I would start. What one deployment unit with real internal boundaries buys you — and how that design deteriorates.Edition 2 cover: “Modular Monolith — the disciplined middle ground”. One application box contains order, payment, user and inventory modules above a shared database, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  3. Microservices: Independence Has an Operational CostAugust 31, 2026Microservices solve organizational and scaling problems, not fashion problems. The operational responsibilities that arrive with a distributed system, and the question worth asking instead of “should we use microservices?”Edition 3 cover: “Microservices — independence with operational cost”. APIs, gRPC and messaging feed order, payment, user and inventory services, each with its own database, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  4. Event-Driven Architecture: React Without Making Everything WaitSeptember 1, 2026Sometimes the fastest way to scale a workflow is to stop making every system wait for every other system. Events do not remove complexity — they relocate it, and the relocation has to be designed.Edition 4 cover: “Event-Driven Architecture — react in real time”. An order service publishes to an event bus that fans out to payment, inventory and notification consumers, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  5. Service-Oriented Architecture: The Lessons Still MatterSeptember 2, 2026Before microservices became fashionable, enterprises were already trying to solve service boundaries. What SOA got right, what it taught us the hard way, and why dismissing it as old architecture misses the point.Edition 5 cover: “Service-Oriented Architecture — enterprise integration before cloud-native”. Mobile, web, ATM, support and branch systems feed an enterprise service bus that routes to customer, payment and account services, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  6. Microkernel Architecture: Keep the Core SmallSeptember 3, 2026Keep the core small, then extend capability around it. Why a stable core with disciplined extension contracts lets teams innovate at the edges — and what turns a plug-in ecosystem into version drift.Edition 6 cover: “Microkernel Architecture — keep the core minimal”. A minimal core application sits at the centre with four plug-in features attached by dashed connectors, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  7. Space-Based Architecture: When Memory Becomes Part of the DesignSeptember 4, 2026At high transaction volumes the database can become the system's shared bottleneck. What it means to move frequently accessed state into a distributed in-memory grid, and the responsibilities that come with it.Edition 7 cover: “Space-Based Architecture — move bottlenecks out of the database”. User, order and payment services feed an in-memory data grid above four processing nodes and a persistent store, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  8. Pipeline Architecture: Make Every Stage ObservableSeptember 7, 2026Complex work becomes easier to manage when it moves through clear stages. The strength of a pipeline is not sequential execution — it is being able to understand and operate the flow.Edition 8 cover: “Pipeline Architecture — value is added in stages”. Data input passes through numbered transform, process and finalize stages to an output box above a conveyor belt, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  9. Data Platform Architecture: Storage Is Not the ProductSeptember 8, 2026Many AI problems eventually reveal themselves as data problems. Organizations often begin with the model; I usually look underneath it. What separates a data lake from a data platform.Edition 9 cover: “Data Platform Architecture — data is the foundation beneath analytics and AI”. Six numbered layers run from sources through ingestion, storage, processing and a semantic layer to consumers, with governance, security and data quality alongside, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.
  10. Architecture for AI and Agents: Models Are Only One LayerSeptember 9, 2026The model may be the most visible component of an AI system, but it is only one part of the architecture. What changes when agents stop generating text and start taking actions.Edition 10 cover: “Architecture for AI & Agents — intelligence needs a real operating model”. A stack runs from user interface through an agent orchestration layer, tools and APIs, a data layer and models to human review, flanked by governance and observability columns, beside short lists of why the pattern matters, what it suits and what to watch for. Neeraj Kumar's portrait and signature appear on the card.

Back to the series

Get in touch

Want this applied to your stack?

The Discovery Audit starts with a free 30-minute discovery call — we tell you honestly whether an audit is warranted before anyone commits a dollar.

Learn about the Discovery Audit