Stars: 120
Forks: 7
Pull Requests: 272
Issues: 29
Watchers: 9
Last Updated: 2023-08-31 15:07:26
Gacela helps you separate your project into modules, focusing on the infrastructure or application layer decoupled from your domain.
License: Other
Languages: PHP, Shell
VISION: Simplify the communication of your different modules in your web application.
MISSION: Normalize the entry point of a module, without interfering with your domain-business logic.
Splitting your project into different modules help in terms of maintainability and scalability. It encourages your modules to interact with each other in a unified way by following these rules:
composer require gacela-project/gacela
You can prefix gacela classes with the module name to improve readability. See more about gacela.
An example of an application structure using gacela modules:
application-name
├── gacela.php
├── config
│ └── ...
│
├── src
│ ├── ModuleA
│ │ ├── Domain
│ │ │ └── ...
│ │ ├── Application
│ │ │ └── ...
│ │ ├── Infrastructure
│ │ │ └── ...
│ │ │ # These are the 4 "gacela classes":
│ │ ├── Facade.php
│ │ ├── Factory.php
│ │ ├── DependencyProvider.php
│ │ └── Config.php
│ │
│ └── ModuleB
│ └── ...
│
├── tests
│ └── ...
└── vendor
└── ...
You can check the full documentation in the official website.
You can see examples using gacela in this repository.
You are more than welcome to contribute reporting issues, sharing ideas, or contributing with your Pull Requests.
Inspired by Spryker Framework: https://github.com/spryker