ConfigCat vs. IBM DevOps Code ClearCase vs. Angular Feature Flags

If you are looking for an experimentation/feature flag style tool that is quick to adopt and provides enough functionality for light/medium use cases, then this is the tool for you. Additionally, they are growing and expanding their functionality and feature set so they can grow alongside you and your needs. The publicly accessible roadmap is also a great benefit to see where time is being spent on which feature next.

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

Feature Flags are well suited for apps which are being developed across numerous teams in order to extend and basically enable/disable whatever areas of the app you want. It's not really necessary for an individual developer or perhaps even a single team of developers, depending.

Incentivized

• Fast and easy feature toggling that gets developers developing
• World class support in both speed and quality for how to best use the service
• Great ear for customer needs and fast paced development

• 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

• Allows for easy configuration of what you may define as features
• Allows for a customization layer to utilize Feature Flags

Incentivized

• No automatic push for flag changes - have to write our own webhooks
• No scheduling interface for flipping flags automatically on a schedule
• Interface is a bit cluttered for people who are just flipping flags

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

Incentivized

• Would be nice if there were a built in route guard and more end to end solution out of the box I suppose

Incentivized

ConfigCat has done the job, and has been great to work with.

Just everything from the website to locating what i need (docs) specific to my platforms is super easy. Not to mention the support articles answering previous questions

They have a community Slack channel that is open to anyone. They always seem to have people in there, even over the weekends and are always happy to answer any questions you have,

At iBinder we searched for and vetted several suppliers of a feature toggle service to handle feature toggling in our production environment. In addition to our functional requirements, it was crucial for us to find a partner that could deliver an EU-compliant service. We finally decided to sign a service agreement with ConfigCat. This has been a real success story for us – in addition to being compliant, ConfigCat delivers an amazing, flexible, and reliable service. They continue to impress by also being very transparent and having a fantastic support and they are very solution oriented and accommodating when it comes to our feature requests etc. We have now used ConfigCat for approximately 2 years and we give our warmest recommendations to anyone who needs a stable, reliable and EU-compliant feature toggle service.

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

We still utilize Git as our source control system but Feature Flags allow us to use Git in a less complex and more efficient way for our development needs.

Incentivized

• Allowed us to migrate seamlessly from a major customer communication system to another, reducing end-user friction and production bugs by being able to turn features off if they didn't work as intended.
• We went from zero experimentation to running 10-20 experiments concurrently across systems. Engineering teams are thinking in an experimentation mindset.

• 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

• I would say a large ROI considering the reduction in branching and merging we need to perform and also the ability to use common, up to date code across teams. There's a lot of shared code we make use of, particularly with identity and authentication and our entire identity platform which is essentially used by each feature.

Incentivized