BestHub
Sign in
Tagged articles

modular monolith

11 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Aug 28, 2026 · Backend Development

Why Service Boundaries Fail: Aligning Business Rules, Data Ownership & Team Topology

This article explains why effective service boundaries require aligning business rules, data ownership, change rhythms, and team responsibilities—not just drawing boxes around nouns—using a refund processing case study to compare modular monolith vs. microservice trade-offs and verify boundaries through concrete evidence.

Domain-Driven DesignMicroservicesarchitecture-design
0 likes · 21 min read
Why Service Boundaries Fail: Aligning Business Rules, Data Ownership & Team Topology
Data Bricklaying Diary
Data Bricklaying Diary
Aug 27, 2026 · R&D Management

System Architecture Isn't Tech Selection: The Critical Questions for Production Readiness

This article argues that system architecture starts from business goals and quality attributes, not technology choices, using a refund processing example to illustrate trade-offs across system boundaries, collaboration patterns, and six architectural perspectives, emphasizing that observability, fault tolerance, and security must be designed in and validated with independent evidence throughout the system's lifecycle.

Microservicesarchitectural trade-offsevidence-based validation
0 likes · 20 min read
System Architecture Isn't Tech Selection: The Critical Questions for Production Readiness
ZhiKe AI
ZhiKe AI
Jun 11, 2026 · Backend Development

Monolith Isn’t the Problem—It’s the Big Ball of Mud

The article argues that monolithic architecture is not inherently flawed; the real issue is a “big ball of mud” lacking clear module boundaries, and it explains how the MonolithFirst principle, an architecture spectrum, modular‑monolith design rules, and real‑world case studies guide teams to choose the right structure.

Microservicescase studymodular monolith
0 likes · 13 min read
Monolith Isn’t the Problem—It’s the Big Ball of Mud
21CTO
21CTO
Jan 31, 2026 · Backend Development

Why Microservices May Be Overkill: Embrace Modular Monoliths for Simpler, Faster Deployments

The article examines how the rise of microservices introduced hidden complexity, cost, and operational overhead, and argues that many teams are shifting back to modular monoliths, which offer clearer boundaries, faster deployments, and lower coordination burdens while still supporting future scalability.

Backend DevelopmentMicroservicesmodular monolith
0 likes · 14 min read
Why Microservices May Be Overkill: Embrace Modular Monoliths for Simpler, Faster Deployments
LuTiao Programming
LuTiao Programming
Jan 25, 2026 · Backend Development

12 2026 Java & Spring Boot Trends Reshaping Backend Development

The article outlines twelve concrete shifts—cloud‑native defaults, Project Loom virtual threads, selective reactive use, AI‑assisted coding, API‑first design, built‑in observability, modular monoliths, security‑by‑design, native images, confidence‑driven testing, DDD revival, and a move from code writing to system judgment—that will define Java backend engineering by 2026.

AI codingCloud NativeJava
0 likes · 8 min read
12 2026 Java & Spring Boot Trends Reshaping Backend Development
FunTester
FunTester
Sep 2, 2025 · Backend Development

How Adaptive Modular Monoliths Enable Seamless Service Splitting

The article explains how adaptive modular monolith architecture lets teams develop quickly with a single deployable unit and later split modules into independent microservices by merely changing a configuration, eliminating repackaging, complex pipelines, and code modifications while preserving performance and simplicity.

MicroservicesService Splittingmodular monolith
0 likes · 7 min read
How Adaptive Modular Monoliths Enable Seamless Service Splitting
JavaEdge
JavaEdge
May 13, 2024 · R&D Management

Why Team Autonomy Is Critical for Fast, Reliable Software Delivery

The article explains why granting software teams independent decision‑making power speeds up delivery, reduces coordination overhead, and outlines three architectural approaches—loosely coupled subdomains, modular monoliths, and microservices—to achieve effective team autonomy.

ArchitectureMicroservicescoordination overhead
0 likes · 6 min read
Why Team Autonomy Is Critical for Fast, Reliable Software Delivery
JD Tech
JD Tech
Sep 5, 2023 · Fundamentals

Layered Monolithic Architecture: Styles, Benefits, and Common Issues

This article examines the layered monolithic architecture style, describing classic four‑layer and five‑layer designs, their advantages and drawbacks, the impact on system complexity, change isolation, and the gap between business domains and technical implementation, and proposes modular monolith approaches to mitigate these challenges.

change isolationlayered designmodular monolith
0 likes · 13 min read
Layered Monolithic Architecture: Styles, Benefits, and Common Issues
21CTO
21CTO
Feb 18, 2023 · Backend Development

Can Modular Monoliths Outperform Microservices? Exploring Spring Modulith

This article examines how modern modular monoliths, especially Spring Modulith, can provide scalable, low‑overhead alternatives to microservices by isolating modules, reducing remote calls, and simplifying deployment while addressing common concerns about complexity and performance.

Spring Modulithbackend architecturemodular monolith
0 likes · 13 min read
Can Modular Monoliths Outperform Microservices? Exploring Spring Modulith