proomt

Search

Search posts, papers, and topics

All posts

Freek Van der Herten1 min readintermediate

Modular Monoliths: Creating Real Boundaries Before Reaching for Microservices

Read on freek.dev

Summary

A high‑level overview of modular monoliths, covering module APIs, database ownership, cross‑module communication, architecture tests, incremental migration, and when to consider moving to microservices. The article provides little concrete implementation detail or measured results.

  • Modular monoliths are presented as a stepping‑stone before adopting microservices.
  • Key concepts mentioned: module‑level APIs, each module owning its data, and explicit cross‑module communication contracts.
  • Advocates architecture tests to enforce module boundaries.
  • Suggests incremental migration paths from monolith to microservices based on clear signals.

Understanding how to enforce real boundaries inside a monolith can reduce coupling and make future service extraction less risky, a common pain point for teams scaling Laravel applications.

3/10
architecturemicroservicesphplaravelmodular monolith

Related reading

  1. Microservices vs Monolithic Architecture: What Nobody Tells You Until You've Lived Through Both

    The article walks through the hidden costs of both monoliths and microservices, showing that the choice isn’t about hype but about concrete trade‑offs like deployment coordination, observability, data consistency, and team structure. It recommends a modular monolith as a pragmatic middle ground when the organization isn’t ready for full service sprawl.

    SitePointsitepoint.com9 min

  2. Article: Your Next DSL Author Is a Language Model

    Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…

    InfoQinfoq.com18 min

  3. Article: Beyond Relevance: A Governance-First Architecture for Enterprise Personalization

    The article proposes a governance‑first architecture for enterprise personalization, where policy‑driven steps (memory, journey graph, AI routing, scoring, trust checks, outcome simulation) shape the recommendation before it is returned. A reference FastAPI implementation demonstrates the pattern with external YAML policies and optional LLM assistance.

    InfoQinfoq.com19 min

  4. Why Releasing Software as an Application Beats Deploying Components

    This article argues that independent microservice deployments, while seemingly fast, often lead to complex and fragile releases due to environment drift and implicit dependencies. It advocates for "application-level releasing," where a consistent, validated snapshot of interdependent components is promoted together across environments to restore predictability and stability.

    Codeshipcloudbees.com5 min

  5. EP226: API Concepts Every Software Engineer Should Know

    This article outlines essential API design considerations, covering HTTP fundamentals, architectural styles like REST and GraphQL, and critical aspects such as naming, versioning, security, and reliability. It serves as a high-level checklist for engineers designing or consuming APIs.

    ByteByteGobytebytego.com5 min

  6. Building Composite Model Context Protocol (MCP) Gateways in TypeScript

    Step‑by‑step tutorial showing how to build a stateless composite Model Context Protocol (MCP) gateway in TypeScript using Hono, Zod, and the MCP SDK. It covers config‑driven upstream registration, namespaced tool discovery, JSON‑RPC routing, per‑tool auth middleware, and a token‑bucket rate limiter, with concrete code snippets and design trade‑offs.

    SitePointsitepoint.com16 min