https://wid-blog.github.io/en/categories/design-pattern/Recent content in Design Pattern on wid's blogHugoenSat, 15 Feb 2025 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/circuit-breaker/Sat, 15 Feb 2025 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/circuit-breaker/A Circuit Breaker’s trip trigger and recovery strategy must be designed together. Trip without recovery cuts the dependency permanently; recovery without a trip basis becomes meaningless cycling.https://wid-blog.github.io/en/posts/tech/design-pattern/rate-limiting/Fri, 14 Feb 2025 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/rate-limiting/Before choosing a rate limit algorithm, the protection layer decides which algorithms are even available. This post lays out how L4/L7/Application layers and Token/Leaky/Sliding/Fixed algorithms intersect.https://wid-blog.github.io/en/posts/tech/design-pattern/builder/Sun, 11 Feb 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/builder/Builder is the answer when three limits of constructors meet at once — many parameters, some optional, and step-wise validation. With fewer than all three, simpler tools suffice. When the language provides rich named/default parameters, the need for Builder shrinks as well.https://wid-blog.github.io/en/posts/tech/design-pattern/factory/Sun, 04 Feb 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/factory/Factory’s shared intent is separating creation from use. The three variants — Factory Method, Abstract Factory, and Static Factory Method — split creation differently and suit different conditions. Static Factory Method is the variant most often encountered in practice, and DI containers absorb part of Factory’s explicit role.https://wid-blog.github.io/en/posts/tech/design-pattern/singleton/Sun, 28 Jan 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/singleton/Singleton is one of the simplest patterns but the canonical anti-pattern debate. The decision to bundle single-instance guarantee with global access into one pattern causes tight coupling and test difficulty. DI is the general alternative that separates the two intents.https://wid-blog.github.io/en/posts/tech/design-pattern/dependency-injection/Thu, 25 Jan 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/design-pattern/dependency-injection/DIP (principle), IoC (pattern), and DI (technique) sit at different levels of abstraction. The hierarchy must be clear before framework features and design principles can be told apart.