@Jobst4Media @ongdb Enduring lawsuits for that last two years has been stressful. While the days ahead are still challenging there is much more clarity and resolve that gives me hope for greater things to come. I have already experience a weight lifting that has made work exciting again.
Special thanks to @jmsuhy for all the efforts in getting this release out. Very excited about the #neo4j community efforts to move the mission forward to keep neo4j open source. Thanks everyone!
First downloadable glimpse at what's coming in Neo4j 4.0.
Dedicated to all those whose lives might improve if Neo4j were to support fine-grained authorization, reactive drivers, and multiple databases per instance/cluster:
https://t.co/o1YMVcywBS
#Neo4j#NoSQL#BigData
Unfortunately @Neo4j Inc has mislead and deceived the US government regarding neo4j licensing and open source usage. The public will be learning about this soon. (Ongoing lawsuit). I wonder if @USArmy and @NASA know about this?
Open Neo4j Enterprise codebase for 3.5 can be found here: https://t.co/WGEIn5k0oV
Status of ONgDB Licensing: graphfoundation/ongdb#3
ONgDB Project Site: https://t.co/CPtocLoRLU
We're getting a lot of inbound asking why the #Neo4j Enterprise source code has disappeared in 3.5 after 10 years of open source development. Answers and the path forward here https://t.co/wWanFGpJmW
The Graph Foundation is continuing forward development of open source #Neo4j Enterprise under the #ONgDB Project. You can read TGF response to @neo4j taking enterprise closed here: https://t.co/tV35s1ITtz
Graph Hack Exclusive to start off the New Year. If you're already building with graph (#ONgDB/#Neo4j) or interested in creating an app you don't want to miss this! https://t.co/LGI80SVbj7 #Meetup#SantaMonica
Huh. So @neo4j removed #AGPL licensed open source code with $80MM Series E in hand after 8 years of commercializing on top of #OSS and the #Neo4jCommunity. To me this is unethical. I'd like to think some folks @fsf and @neo4j are just a little troubled by this as well.
Latest #neo4j APOC project on 3.5 fails to build unless you have access to proprietary Neo4j Enterprise repos. A world where #AGPL open source can be taken closed in an instant is a dangerous one for everyone. @neo4j is a case of bad ethics on a slippery slope.
@emileifrem@jimwebber@mesirii@neo4j Yes, Neo4j Enterprise has always been open source under AGPL and commercially supported under the Neo4j Commercial License. By moving to open core you've made many important features private and now introduced a closed database format in Enterprise. How is that the future vision?
@emileifrem@jimwebber@mesirii@neo4j - did you know you that open source enterprise is missing from the #neo4j github? Who had a say in moving to closed source? It’s important for the community to know the individuals that made this decision.
A modern data architecture needs an open source database that has clustering, monitoring, backups, restore, security, drivers, query language, scalability and performance. This has always been the case and #Neo4j never becomes as relevant without these features being open source.
@prathle You're glossing over a huge problem here. #Neo4j isn't a viable database without the open source enterprise features. This was the case way back in 1.8 (2012) when clustering with HA paxos was introduced and it's still the case now. https://t.co/qwojOOlIzX
And #Neo4j Enterprise uses a separate database format that once migrated to is no longer compatible with Community. You've effectively locked-in all Enterprise customers to a proprietary data format if they upgrade to 3.5 Enterprise. It's unethical not to disclose this fact.
Sneak preview: Case Study is on ingesting financial exchange data through an event driven pipe to continuous ML model training and prediction. #DASummit#GraphCloud