Javarevisited·1yS.O.L.I.D Principle Part 1
An introduction to the S.O.L.I.D principles which are fundamental for software design patterns. This part covers the Single Responsibility Principle, Open Closed Principle, and Liskov Substitution Principle, explaining how these principles enhance flexibility, maintainability, and modularity in code. Examples and practical use cases are provided to illustrate these principles.
Code Maze·1yChain of Responsibility Design Pattern in C#
The Chain of Responsibility design pattern breaks down logic into smaller components with distinct responsibilities, chaining them together to accomplish a task, promoting the Single Responsibility Principle and loose coupling. This pattern's implementation in C# is demonstrated through a rental request processing API. The post also highlights its advantages, such as workflow synthesis, and challenges, such as dependency order and possible request handling gaps.
Baeldung·1yWhat Is chain.doFilter() Doing in Spring Filter?
This tutorial explains the purpose and importance of the chain.doFilter() method in the Spring framework. It covers the concepts of filters and filter chains, outlining common use cases for filters like authentication and logging. The article also connects the chain.doFilter() method to the Chain of Responsibility design pattern. Step-by-step guidance on creating and registering custom filters in Spring is provided.
DEV·1yIt’s Not Flutter
The author discusses their preference for not using the BLoC pattern in Flutter, favoring a simpler approach aligned with Flutter's inherent design patterns like MVC and PAC. They introduce the StateX class and StateXController to manage states more efficiently in a Flutter app. The post includes a comparison between the BLoC pattern and the proposed method, emphasizing the simplicity, modularity, and maintainability of using StateX and StateXController.