0 views collected around this technical thread.
This article analyzes the high coupling caused by multiple backend controllers and third‑party push interfaces, then proposes a dedicated TPS microservice that encapsulates third‑party calls via Feign, standardizes parameters, and reduces code duplication for frontend and backend systems.
This article analyzes the coupling problems caused by multiple controller calls and third‑party push interfaces, proposes a TPS microservice to centralize third‑party interactions, demonstrates Java Feign interfaces and enum‑based routing, and shows how backend and frontend can achieve low‑coupling architecture while reducing code duplication.
The article explains how high coupling caused by multiple front‑end controllers and repetitive back‑end push‑service code can be eliminated by introducing a dedicated TPS microservice that encapsulates third‑party integrations and exposes a unified Feign interface for all business systems.
Understanding tight and loose coupling in system design, this article explains their trade‑offs, introduces a coupling degree metric based on graph theory, demonstrates calculations with example module dependencies, and discusses when each approach is preferable for performance, maintainability, and scalability.
The article analyzes coupling problems caused by multiple backend controllers and third‑party push interfaces, proposes a dedicated TPS microservice to encapsulate third‑party calls, demonstrates Feign integration with Java code examples, and concludes with a summary of benefits and further considerations.
The article analyzes high coupling problems caused by multiple controller calls and third‑party integrations in a Java settlement backend, and proposes a dedicated TPS microservice with unified Feign interfaces, enum‑based routing, and factory patterns to decouple frontend and backend logic while providing implementation examples and diagrams.
This article explains the concept of coupling, demonstrates how traditional object creation leads to high coupling, and shows how using interfaces, the factory pattern, and reflection—culminating in Spring IOC—can dramatically lower coupling, improve reuse, and simplify maintenance in Java backend development.
Software teams often grow to handle rising workload, yet adding features makes development exponentially harder because essential complexity dominates, hidden feature coupling and inevitable code decay increase system intricacy, and only refactoring, anti‑corrosion practices, and thorough documentation can mitigate the resulting business system complexity.
This article explains the different types of coupling in microservice architectures, compares RPC and event‑driven communication, discusses event notification and event sourcing, and offers practical guidance on reducing tight coupling, designing service gateways, and deciding the appropriate number of microservices.
The article explains the concept of software testability, outlines controllability and observability factors, discusses cohesion and coupling, suggests practices such as TDD and design patterns, and introduces tools like testability‑explorer and Sonar for measuring and enhancing testability.
This article explains software design patterns, their origins, key examples, and how MITRE system engineers can apply them to manage coupling and interface design in large enterprise service environments, emphasizing loose coupling, best‑practice guidelines, and practical lessons learned.
The article examines synchronous request‑response microservices, outlining their numerous drawbacks such as tight coupling, scalability limits, failure handling, API versioning challenges, data access coupling, distributed monolith risks, and testing difficulties, while also acknowledging their undeniable advantages and the prevalence of hybrid architectures.
This article explains the concept of coupling in object‑oriented programming, distinguishes strong and weak coupling with Java examples, and presents two practical techniques—upcasting/interface callbacks and the adapter pattern—to achieve low coupling and improve code modularity.
The article explains the concepts of modules, coupling, and cohesion, outlines key interface design principles such as Single Responsibility and Dependency Inversion, and illustrates these ideas with practical examples of design patterns like Facade, Bridge, and Adapter, including code snippets.
The article explains how microservices communicate via RPC or event‑driven approaches, analyzes different coupling types, compares event notification and event sourcing, discusses API‑gateway and service composition, and offers practical guidance on limiting microservice count and using internal microservice design.
This article explains core OO architecture principles such as low coupling and high cohesion, outlines methods to reduce coupling, advocates composition over inheritance, and provides concise overviews of widely used design patterns like MVC, MVVM, Factory, Singleton, Builder, and many others.