Tagged articles
7 articles
Page 1 of 1
IT Architects Alliance
IT Architects Alliance
Sep 19, 2025 · Fundamentals

Why Loose Coupling Is the Secret Sauce Behind Scalable Architecture

Loose coupling, a design principle that minimizes inter-component dependencies, enables scalable, testable, and flexible systems by using clear interfaces, event-driven architectures, API gateways, and service meshes, while also presenting trade‑offs such as added complexity, performance overhead, and consistency challenges in distributed environments.

MicroservicesScalabilitySoftware Architecture
0 likes · 12 min read
Why Loose Coupling Is the Secret Sauce Behind Scalable Architecture
Model Perspective
Model Perspective
Jul 2, 2024 · Fundamentals

How to Quantify Tight vs Loose Coupling with Graph Theory

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.

CouplingSoftware ArchitectureSystem Design
0 likes · 6 min read
How to Quantify Tight vs Loose Coupling with Graph Theory
21CTO
21CTO
Dec 1, 2022 · Backend Development

Why Go Skips Frameworks: Leveraging Unix Philosophy for Faster, Maintainable Services

The article argues that Go deliberately avoids heavyweight frameworks by following the Unix philosophy of small, composable tools, discusses the trade‑offs of time‑saving versus long‑term maintainability, and shows how building services with minimal libraries can lead to looser coupling and faster delivery.

Backend DevelopmentUnix Philosophyloose coupling
0 likes · 10 min read
Why Go Skips Frameworks: Leveraging Unix Philosophy for Faster, Maintainable Services
DevOps
DevOps
Aug 24, 2020 · Fundamentals

Understanding Loose Coupling in Banking IT Systems: Concepts, Measurement, and Design Practices

This article explains the concept of loose coupling in banking IT systems, outlines its definitions, measurement criteria, and practical design guidelines across components, interfaces, data, and processes, while also discussing the trade‑offs and costs associated with adopting a loosely coupled architecture.

Software ArchitectureSystem Designbanking IT
0 likes · 16 min read
Understanding Loose Coupling in Banking IT Systems: Concepts, Measurement, and Design Practices
ITPUB
ITPUB
Oct 12, 2019 · Backend Development

8 Essential Principles for Designing a Business Middle Platform

This article outlines eight core principles for designing a business middle platform, covering service loose coupling, dependency management, design guidelines, naming, granularity, statelessness, operation design, and constraint rules to ensure scalable, maintainable, and business‑aligned services.

Backend ArchitectureMicroservicesloose coupling
0 likes · 11 min read
8 Essential Principles for Designing a Business Middle Platform
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Jul 8, 2017 · Fundamentals

What Makes SOA So Powerful? Uncovering Its Core Principles and Benefits

Service‑Oriented Architecture (SOA) is a loosely‑coupled, coarse‑grained architectural model that enables distributed deployment and reuse of services through standardized interfaces, offering benefits such as external accessibility, high availability, scalability, and easier maintenance, while emphasizing service contracts, message patterns, and design management.

SOASoftware Architectureenterprise integration
0 likes · 16 min read
What Makes SOA So Powerful? Uncovering Its Core Principles and Benefits

Can Disposable Code Outperform Reusable Code? A Deep Dive into Maintainability

The article argues that treating lines of code as a cost rather than a product encourages writing disposable, loosely‑coupled software, and it walks through practical stages—from avoiding code entirely to using feature flags—to build systems that are easier to modify, replace, or discard.

code maintainabilitydisposable codefeature flags
0 likes · 20 min read
Can Disposable Code Outperform Reusable Code? A Deep Dive into Maintainability