Choosing a Java Package Structure

├── com.java └── company ├── Company ├── CompanyController ├── CompanyRepository └── CompanyService └── product ├── Product ├── ProductController ├── ProductRepository └── ProductService └── user ├── User ├── UserController ├── UserRepository └── UserService ├── com.java └── controller ├── CompanyController ├── ProductController └── UserController └── model ├── Company ├── Product └── User └── repository ├── CompanyRepository ├── ProductRepository └── UserRepository └── service ├── CompanyService ├── ProductService └── UserService

A child stands at a fork in a cartoon path while two competing Java package structures are shown above. The joke contrasts organizing code by domain entity—company, product, and user—with organizing it by architectural layer—controller, model, repository, and service. It is used as a humorous reaction to debates about package structure and software architecture.

• @gentoomemes / 9963 2024-03-14
• @right_wing_dev_squads / 13671 2026-01-09