How to choose dependencies for stability
Modern applications are built up of dozens or even hundreds of building blocks created by other programmers. Welcome to dependency hell! Now how do you get through?
First things first. Don’t get caught up on how many options there are or every single feature, you’ll lose valuable time that should be spent on new development. The only perfect choice will probably be the one you build yourself. But unfortunately if we always build everything ourselves we’ll never finish anything. So how do we choose?
Choose the right attributes
These do not apply to every application but these are the things I value most building something sustainable. Depending on how vital the component is you should spend more or less time researching each of these.
Read the docs, follow a tutorial for a sample application, the better a project is the easier this will be.
You will encounter problems, it’s just part of programming. A good community will go a long way towards helping with this.
- Is the projects responsive to bug reports? What’s the process?
- Do users participate in live chat?
- Are questions regularly answered and asked on Stack Overflow?
Don’t let your schedule be held back by your imports. For anything mission critical review anything that might cause unexpected maintenance.
- Review the upgrade path between versions, the more documentation the better!
- How is the backward compatibility between versions.
- How frequent is the release cycle?
In general anything FOSS will be alright to use but you should probably become familiar with the common ones so that you can quickly identify them. Github published a handy website for learning more about the most common types.
Learning how to analyze a project’s track record can help you to predict where it’s going.
Mature Projects (4+ years)
Projects that are sponsored by an open source organization such as the Apache Foundation are usually very reliable, they’ve been accepted by a reputable organization and are likely being actively maintained by the community. You can likely expect a strong degree of stability, community support, and very often one or more companies providing support & consulting services. Corporate sponsored projects are more hit and miss and should be reviewed individually based on the companies individual history.
Young Projects (1-3 years)
Maturity comes with age, young projects even if they appear to be stable should be handled with care. I wouldn’t recommend them for anything that cant be easily replaced.
Personal Projects (any age)
Only use one of these if your comfortable contributing back or forking the entire thing. For small components this is probably fine but for essential pieces of your application you might want to choose something with a better record.