Composer vs. Rudder

I do highly recommend it whenever you have some PHP projects, especially if you need to have reusable modules that you want to share across teams. With a good branching an tagging strategy, you can go a long way in making your developers' life easier. They will only need to work on the modules that are of interest of them, and not have to touch the whole codebase.

Also, it's quite necessary if you are planning to use community PHP modules, as the vast majority of them is distributed, and versionned via packagist.org, and thus via composer.

Incentivized

• Controlling dependencies
• Fast dependency resolver
• Easy to use dependency injection

Incentivized

• Sometimes a bit slow, but v2 made a lot of improvements on that
• If everything is modular, setting up a local dev environment is a bit trickier than having everything in the same repo
• Might be hard to adopt with some frameworks which have not fully embraced it, like Wordpress

Incentivized

If you're familiar with npm or Yarn, you'll feel right at home with composer. The work in pretty much the same way. You can use a composer.json file in your repo to reference specific version of public community modules, and enterprise internal ones. You can also hook some scripts that you would want to execute, like for testing, building your code ...

Incentivized

• Composer only has had positive impacts in our business. It saves a lot of time and resource in order to develop a software.

Incentivized