LEGO Architecture ใน Flutter วิธีจัดโค้ดให้ต่อได้เหมือนตัวต่อ

LEGO Architecture and Clean Architecture: A Unique Approach to Code Organization by Nokka (นก-กา)

In a recent article on freeCodeCamp, Nokka explained why this concept exists and how to implement it effectively. The author opened by showing an image of two LEGO bricks being connected.

The key idea behind this approach is that LEGO bricks have two main characteristics: shape, color, purpose, and connectors. Similarly, in a Flutter application, a module (widget, class, service, or feature) plays the role of the connector, while the shape, color, and purpose describe its functionality.

Modules in the code depend on each other through these connectors. For instance, Padding is a module that only depends on its child widget, which could be a Text, Image, Column, or any other widget. Similarly, the PriceTag module decides on the layout and content of a price display.

The author demonstrated how to create a reusable component, SurfaceCard, that encapsulates a padded container with a rounded border and a child widget. This approach allows for easy reuse and styling without duplicating code.

The core of the article highlights the importance of designing modules based on their responsibilities (features) rather than their types (folders like screens, widgets, and services). By structuring the codebase around features, developers can easily navigate and maintain the application.

The author also emphasized the significance of defining interfaces (abstract classes) to define the capabilities of modules without specifying their implementation details. This enables easy testing and swapping of implementations.

In conclusion, both LEGO Architecture and Clean Architecture follow the principle of dependency inversion, where modules depend on abstractions rather than concrete implementations. The main difference lies in the specific goals they aim to achieve, with Clean Architecture focusing on separating concerns and enhancing testability.