Archetypes

In software development, particularly when following clean code and clean architecture principles, we can identify several common module archetypes. These archetypes serve as patterns or templates for organizing code and responsibilities within a system. Here are some key module archetypes:

1. Entity

• Represents core business objects
• Contains business logic and rules
• Example: Customer, Order, Product

2. Use Case / Interactor

• Implements specific business use cases
• Orchestrates the flow of data between entities and gateways
• Example: CreateOrder, ProcessPayment

3. Controller / Presenter

• Handles input from the user interface or external systems
• Prepares data for presentation
• Example: OrderController, UserProfilePresenter

4. Gateway / Repository

• Abstracts data access and persistence
• Provides an interface for interacting with external systems or databases
• Example: CustomerRepository, PaymentGateway

5. View / UI Component

• Responsible for displaying information to the user
• Handles user interactions
• Example: OrderListView, ProductDetailsComponent

6. Data Transfer Object (DTO)

• Used to transfer data between processes or layers
• Typically contains no business logic
• Example: CustomerDTO, OrderSummaryDTO

7. Factory

• Creates and configures complex objects or object graphs
• Example: ReportFactory, DatabaseConnectionFactory

8. Service

• Provides stateless operations that don’t naturally belong to entities
• Often used for cross-cutting concerns
• Example: EmailService, LoggingService

9. Adapter

• Converts interfaces between different systems or modules
• Example: ThirdPartyPaymentAdapter, LegacySystemAdapter

10. Validator

• Ensures data integrity and business rule compliance
• Example: OrderValidator, UserInputValidator

These archetypes help in organizing code, separating concerns, and maintaining a clean, modular architecture. They provide a common vocabulary for developers and can guide the design of software systems.