Question about packaging

Hey,

I am wondering is it better approach to use packaging by feature instead of packaging by layers using DDD.
In what direction your example packaging expand in the future?

Just by looking at the package structure:

└── library
    ├── catalogue
    ├── commons
    │   ├── aggregates
    │   ├── commands
    │   └── events
    │       └── publisher
    └── lending
        ├── book
        │   ├── application
        │   ├── infrastructure
        │   └── model
        ├── dailysheet
        │   ├── infrastructure
        │   └── model
        ├── librarybranch
        │   └── model
        ├── patron
        │   ├── application
        │   ├── infrastructure
        │   └── model
        └── patronprofile
            ├── infrastructure
            ├── model
            └── web

Does it start to use packaging by feature?

Start by reviewing the package structure shown in the issue and how the example currently groups catalogue, commons, and lending. The issue has no named file, test, or concrete documentation change; a useful outcome would require an explicit decision or explanation of whether and how the packaging should evolve.