Composer vs. IBM DevOps Code ClearCase

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

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

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

Incentivized

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

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

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

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

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

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

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized