anchor.diff:  
   
   
  -That is one way to say it.  Of course, they could have easily just provided a Neo4j Enterprise binary without the intra cluster encryption turned off under it’s AGPLv3 license.
  +That is one way to say it.  Of course, they could have easily just provided a Neo4j Enterprise binary without the intra cluster encryption turned off under it’s https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"].
   
   Security critical components should be open source, security by obscurity has proven not to be a good strategy in the past.
    
  
positive.code: 
  As a reference, look no further than MySQL , or rather what we now call https://mariadb.org/about/[MariaDB , window="_blank"] - the more popular fork of MySQL, and http://www.zdnet.com/article/open-source-mariadb-a-mysql-fork-challenges-oracle/[can see what could happen , window="_blank"].
  
  It looks like Neo4j Inc does not want to tempt fate with a closed source move just yet.   Instead another path was taken which makes it very hard to get ahold of the enterprise packaged binaries with the AGPLv3 license. As a passionate advocate of both open source software and Neo4j - this doesn’t sit well with me. 
  
  Many federal agencies have already invested in the adoption and use of Neo4j Enterprise using it’s free open source license. Luckily, we happen to be Neo4j developers and these moves simply do not affect us or our federal clients because we build the binaries from source already.
  
  