---
title: "Monolithic vs. Composable: Architecture Decisions for Drupal"
lang: en
type: knowledge
canonical: https://www.arocom.de/en/knowledge/drupal/monolithic-systems
alternate: https://www.arocom.de/wissen/drupal/monolithische-systeme
author: "Axel Roth"
last_updated: 2026-07-29
---

# Monolithic vs. Composable: Architecture Decisions for Drupal

Monolithic systems bundle all functions in a shared codebase and
database. This simplifies operations but makes scaling and independent
development more difficult. Drupal is architecturally a monolith with
modular design, a pragmatic middle ground. arocom has been advising
organizations on architecture choices since 2012 and relies on the
solution that fits the project.

## Monolithic vs. Composable: Architecture Decisions for Drupal

A monolithic system is an application in which all functions and
data reside in a shared codebase and database. Changes to one part
can affect the entire system. This makes maintenance and scaling
more costly than with modular architectures.

## Monolith, Microservices, or Modular Monolith?

Microservices split an application into small, independent
services. Each service can be individually scaled, tested, and
deployed. The price: higher complexity in operations, monitoring,
and communication between services.

Drupal is a modular monolith. All functions run in one
application but are cleanly separated through modules. Modules
can be enabled, disabled, and replaced without rebuilding the
entire system. For most web projects, this is the most pragmatic
approach: simple operations with sufficient flexibility.

## When Which Architecture Fits

A monolithic approach with Drupal fits when an organization
needs a central platform for content, permissions, and
workflows. Microservices are worthwhile when different teams
work independently on different components and need to scale
them individually.

arocom recommends: start monolithic with Drupal. If individual
features later need to scale independently, they can be
extracted via APIs. That is more cost-effective than building
a microservice architecture from the start.

## Looking for Architecture Consulting?

The [Future Check](https://www.arocom.de/en/future-check) analyzes your current
architecture and provides a clear recommendation.

**From arocom projects:**

- At [HENN](https://www.arocom.de/en/references/henn) (architecture firm) we put the drupal/ai module into production, AI-powered image tagging and semantic search directly in the backend.
- Hopt + Schuler needs job openings on the careers page in real time, sourced from the JobCluster system. We delivered this via a custom module against the JobCluster API, vacancies appear without manual upkeep, the recruiting workflow runs centrally in JobCluster, the site reads live.

### Is Drupal a monolithic system?

Drupal is a modular monolith. All functions run in one application but are cleanly separated through the module system. This offers the simplicity of a monolith with the flexibility of modular architecture.

### When are microservices better than a monolith?

Microservices are worthwhile when different teams work independently on different components and need to scale them individually. For most web projects, a modular monolith like Drupal is the more pragmatic choice.

## Read more

- [Drupal explained](https://www.arocom.de/en/knowledge/drupal/what-is-drupal): The CMS in detail
- [Drupal development](https://www.arocom.de/en/services/development): Concept and architecture
- [Future Check (Audit)](https://www.arocom.de/en/future-check): Independent analysis