Skip to content
Open access

Tail latency, throughput, and memory overhead of monolithic and microservices architectures in resource-constrained docker deployments

Jul 2026 · JUTI: Jurnal Ilmiah Teknologi Informasi · pp. 200-217 · 0 citations · 26 references

TL;DR

This study compares the implementation of the same backend system, Node.js/Express and MariaDB, in a monolithic and microservices architecture with the same Docker resource allocation, 2 CPUs and 512 MB RAM per architecture, except database containers.

Abstract

Software architecture selection directly impacts system performance and resource efficiency. This motivates controlled comparisons to make pragmatic deployment decisions. This study compares the implementation of the same backend system, Node.js/Express and MariaDB, in a monolithic and microservices architecture with the same Docker resource allocation, 2 CPUs and 512 MB RAM per architecture, except database containers. The load test was carried out with Apache JMeter 5.6.3 with three levels of concurrency (50, 200, 500 users). Each scenario was performed 20 times within 60 s. The main metrics were response time P90, P95, throughput, error rate, CPU/RAM utilization. The monolithic implementation performed better than the microservices at all load levels. The monolith reached P90 131.35 ms and 429.89 req/s versus microservices P90 171.38 ms and 332.38 req/s at 50 users, and P90 1217.60 ms and 438.25 req/s versus 1534.50 ms and 343.24 req/s at 500 users. Statistical analysis All differences were statistically significant (Mann-Whitney U, p < 0.0001, |δ| = 1.000). For both architectures, the throughput plateaued at load levels. The most operationally significant difference in resource usage was in memory overhead at 500 users, the monolith used 95.31 ± 1.99 MiB compared to 319.43 MiB aggregate for microservices (3.35x higher). CPU utilization was broadly comparable across architectures. The results presented here are specific to this experimental configuration, i.e. a single-machine Docker deployment, two-service decomposition, and synchronous HTTP/REST communication, and should not be generalized to monolithic and microservices architectures in general.

Read PDF

Similar papers

Preprint Aug 2026

An Empirical Comparison of Monolithic and Microservices Architectures for an E-Commerce Application

An experimental comparison of a monolithic and a microservices implementation of the same e-commerce application, both backed by a shared PostgreSQL database, suggests that decomposing the system into microservices improves scalability and tail latency under stress, while introducing distinct, service-specific failure...

Swayam Amol Katole · 0 citations
Jul 2026

Performance Evaluation of API Gateways in Microservices System: No Gateway, Kong, and Native

API Gateway selection is a critical architectural decision in microservices systems, yet empirical comparisons between competing gateway strategies are scarce, particularly for PHP-based systems at the SME scale. This study presents a comparative performance analysis of three API Gateway implementations within System X...

Novika Natalia, Rahmat Yasirandi, Sheina Fathur Rahman · 0 citations
Review Open access Aug 2026

Analysis of Microservice Approaches to V2X Systems with Edge Computing

Relevance . The development of V2X systems and the migration of computing toward edge and fog nodes require containerization and orchestration mechanisms; however, the overhead introduced by the orchestration platform itself can reduce the benefit of distributed service placement and is particularly important fo...

G. Tambovtsev, A. Vladyko, P. Plotnikov · 0 citations
Open access 2026

Performance of REST and gRPC in Microservices: Java Blocking vs. Python Non-Blocking I/O

The selection of communication protocols and underlying concurrency models profoundly impacts the performance and resource efficiency of microservice architectures. While existing studies frequently compare protocols like REST and gRPC, they often overlook the compounded effects of language-specific I/O paradigms durin...

A. Noertjahyana, Kartika Gunadi, Joseph Justin Harsono et al. · 0 citations
Conference Jul 2026

WebAssembly on the Cloud Continuum: A Multi-Architecture Evaluation on Kubernetes

This paper presents a systematic, practice-driven evaluation of WebAssembly (WASM) as an execution substrate for cloud-native workloads orchestrated through Docker and Kubernetes using runwasi. We develop a reproducible workflow that compiles Rust and Go/TinyGo applications to WASM modules, applies Ahead-of-Time (AOT)...

Álvaro Vázquez-Rodríguez, David Vila-Pérez, Carlos Giraldo-Rodíguez et al. · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.