1 views collected around this technical thread.
This article explains the classic MVC three‑tier architecture, identifies its drawbacks such as bloated service code and long‑running transactions, and proposes adding a Manager layer to separate generic business processing, improve code maintainability, and enhance performance in Java backend systems.
The article compares MySQL and PostgreSQL multi‑table join capabilities, explains why MySQL’s nested‑loop joins can be less efficient for complex queries, and discusses how decomposing joins into separate single‑table queries or moving logic to the service layer can improve performance, scalability, and caching.
The article examines whether a Service layer in a Spring‑based backend should be defined by interfaces, debunks common arguments for using interfaces, proposes a top‑down coding workflow, explores project structures for single and multiple implementations, and concludes that interfaces are only worthwhile when multiple implementations are required, while also containing promotional material for unrelated services.
This article examines whether a Service layer in a Spring‑based backend should use interfaces, critiques the common justifications, proposes a top‑down coding workflow, explores AOP proxy options, and presents modular project structures for single or multiple implementations.
This article examines whether every Service and DAO class in a Spring‑based backend should implement an interface, discusses the three traditional reasons for using interfaces, explains why they often do not hold up, and proposes practical structuring alternatives for single‑ and multi‑implementation scenarios.
This article examines whether a Service layer in Java Spring projects truly requires interfaces, debunking common arguments, exploring development workflows without interfaces, discussing project structuring for single and multiple implementations, and concluding when interfaces are beneficial or unnecessary.
The article examines MySQL's limited join types and performance drawbacks for multi‑table queries, compares them with PostgreSQL, and explains why many applications split joins into separate service‑layer operations to reduce RPC overhead, improve caching, and handle sharding constraints.
This article explains the purpose and advantages of a service layer between presentation and domain layers, outlines step‑by‑step how to create one in PHP—including directory setup, class and interface definitions, dependency injection—and provides sample code for user management services and controller integration.
The article explains why clear application layering—covering controller, service, manager, and DAO levels—is essential for maintainable backend code, reviews Alibaba's recommended layer structure, proposes an optimized layering model, and discusses domain model conversions to avoid excessive object transformations.
This article presents a senior architect's comprehensive guide to evolving a classic three‑tier backend architecture into a flexible system composed of a gateway layer handling HTTP and TCP protocols, a business layer with services, processes and reusable components, and a foundation layer that defines interfaces and essential technical components such as storage, caching, messaging, transactions, and locking.
The article discusses the importance of clear application layering, outlines Alibaba’s multi‑layer architecture, proposes an optimized layering model, explains domain object types (DO, DTO, BO, AO, VO, Query) and offers practical guidelines to improve code maintainability and reuse in backend development.
The article explains why clear application layering—covering controller, service, manager, and DAO levels—is essential for maintainable backend code, describes Alibaba's recommended layer structure, proposes an optimized layering model, and outlines domain object conventions such as DO, DTO, BO, AO, VO, and Query.
The article compares MySQL's limited join capabilities with PostgreSQL's richer options, explains why multi‑table joins can be slower than separate single‑table queries performed in the service layer, and outlines how decomposing joins improves caching, scalability, and overall system performance.
This article explains how to design a well‑structured Java web application by defining clear three‑layer architecture (Controller, Service, DAO), outlining each layer's responsibilities, describing data type conventions such as PO, BO, VO, DTO, Model, and showing how these types map to the layers for maintainable, scalable development.
The article discusses common pitfalls in application layering, presents the Alibaba coding guideline for multi‑layer architecture, proposes an optimized layering model with clear responsibilities for controller, service, manager, and DAO layers, and explains domain model conversions to improve maintainability and reuse.
This article explains common misconceptions about application layering, outlines essential principles for maintainable layers, details Alibaba's multi‑layer architecture, proposes optimized layering with service and manager responsibilities, discusses domain model conversions, and concludes with practical guidance for clear, reusable backend design.
The article discusses the importance of proper application layering in backend development, critiques common misuse of controller and service layers, outlines Alibaba's recommended multi‑layer architecture—including open API, presentation, web, service, manager, and DAO layers—offers optimization suggestions, and highlights domain model conversions.
This article explains the importance of clear responsibility separation in application layering, reviews Alibaba's recommended layer structure, proposes an optimized layering model, and discusses domain model conversions to improve code maintainability, reusability, and team collaboration.
The article explains the importance of clear application layering, compares Alibaba's recommended multi‑layer architecture with practical optimizations, describes each layer’s responsibilities, discusses domain model transformations, and offers guidelines for maintaining clean, reusable, and maintainable backend code.
The article discusses how abstraction and decoupling through Java interfaces—such as service layers, RPC APIs, and middleware adapters—can improve code maintainability, enable flexible implementation swaps, and clarify responsibilities, while also warning against over‑engineering in most business scenarios.