We have a medium sized Laravel code-base which is separated into multiple modules. Going forward, we plan to separate each module into their own individual packages. The obvious solution would be to host them in Private Packagist. However, that adds another $100 per month to the cost. Alternatively, we could use VCS to define modules in composer.json. We came across a part of this community that prefers this approach. But we are still a little skeptical about it.
@sumihiran I’d first ask why you plan to separate your modules into packages in the first place. Are you actually intending to use these packages in other applications? Or are you just deliberately making working on your medium-sized app more difficult by introducing a complicated workflow that means you need to push packages to then pull them back into your app?
@martinbean The later. However, by separating them into individual packages team get to improve and test each module separately. Each module represent a single bounded context.
@sumihiran You really don’t need to split them out into packages to achieve that. All you’re doing is complicating your development workflow. Because now you’ve got to work on however many “package” codebases, push it up to where ever, to just pull them back down into the “main” application.
Believe me. I’ve seen teams do this in my ~15 years of development and it’s never been worth it.
Please or to participate in this conversation.