profile for Cullen Tsering at Stack Overflow, Q&A for professional and enthusiast programmers

Saturday, November 9, 2013

Questions to ask yourself when choosing an open source solution



As a solutions' architect, I love open source solutions and I love even more incorporating them into the business solutions that I'm designing.  First of all, I don't want to reinvent the wheel, secondly I'd rather focus my dev time on implementing the actually business requirement as much as possible, the time gained by not building it yourself is a great gain for the business and the client.  However, there are so many out there, it can be quite overwhelming and one must be careful when choosing one to use it in your production environment.  The consequence of choosing the wrong one could result in the failure of your project in worst case or to cause delay, drive cost at best.  I have a set of questions, the answers to which really helped me to make a sound decision.

  1. What are others saying about this solution?
    1. Like any other opinion, one must take it with a grain of salt.  Be sure to listen to both the good and the bad.  Either way can be exaggerated or partially true.
  2. Is the solution being successfully used in production by any sizable and reputable company?
    1. I don't know about you but I don't want my clients to be the guinea pig of an open source solution. 
  3. What is the open source license the solution is under?
    1. I've seen open source solutions found on github that will actually require a license fee if you were to use them in commercial products.  So be sure to read the license agreement before investing your time and energy into understanding how it works.  Check out the terms of the different licenses here.
  4. Is the solution being actively developed/maintained?
    1. This one actually goes hand in hand with the first one.  The more people use it the more actively and better it is maintained.
  5. What does the source code quality look like?
    1. Go clone/download the source code and the look at the quality of the code base.  One really good indicator is the test coverage and of course reading the code itself.
  6. How well is it documented and how well is the documentation is updated? 
    1. Obviously this is huge, without it you might as well rewrite the solution yourself.
  7. Is there a good community / support group for it?
    1. Being open source, you'll need questions answered quicker than you can find it on your own.  Otherwise, your productivity would be shot!
  8. Who is behind the project?
    1. For instance, Google is behind AngularJS and Microsoft is behind a bunch of open source initiatives.
    2. This is good indicator but not always the case so this should be weighed by the answers to the other questions.  Big companies are known to pull plugs on projects open source or not.
Hope this will help guide you when trying to choose an Open Source solution.

No comments:

Post a Comment

About Cullen

My photo
Christian, Father, Software Developer/Architect who enjoys technology and using it to make people's lives easier!

Followers