Neo Technology has released version 1.3 GA (General Availability) of Neo4j, a graph-style database.
In creating this new version, the Neo4j team had two goals in mind. The first was a change in licensing. The Community version of Neo4j is now licensed under GNU General Public License (GPLv3). The Advanced and Enterprise editions are available under GNU Affero General Public License (AGPLv3) or commercial licensing. Neo Technology Chief Scientist Jim Webber says the new licensing will allow open access to the community edition.
We believe that graphs are very broadly applicable to an awful lot of computing domains, and yet nobody (including us) has up until this point made graph databases universally free to use and tinker with. We think that's incredibly important since it completely opens up the whole field of graph databases to commercial organizations, researchers, students, and tinkerers and hackers.
According to Webber, the second goal was creating a more developer- and dev-ops-friendly product.
The second theme we had for our 1.3 release was to make the database friendlier (and that's a theme that will continue in future releases). Although the graphistas can naturally think in graphs, we understand that for folks coming from a relational or KV/document background, the simplicity and expressiveness of graphs can (ironically) take a bit of getting used to. I think of it as the injury that lingers once you've taken off the handcuffs.
Some highlights of the Neo4j 1.3 release:
- Each database can now contain 32 billion nodes or relationships and up to 64 billion properties.
- Reduction of the database footprint by implementing a new strategy for common short strings
- The WebAdmin tool for exploring graphical relationships has been revamped
- Faster searches using Dijkstra’s algorithm to find the shortest path between nodes
- Updates to indexing API and underlying implementations
- Enhancements to the REST API
/filters:no_upscale()/sponsorship/topic/2c0d72d2-1768-47c2-8f5b-24f3ef0ae0e0/QconNYrsb-1679560094156.png)
/articles/gdpr-with-spring-and-aop/en/smallimage/easy-implementation-of-GDPR-with-aspect-oriented-programming-small-1684505109873.jpg)
/articles/open-source-java-profilers/en/smallimage/unleash-power-of-open-source-java-profilers-small-1681206807197.jpg)
/articles/rmi-to-websocket/en/smallimage/migrate-a-RMI-based-legacy-application-to-WebSocket-small-1680106723513.jpg)
/articles/rapid-startup-of-your-cloud-native-java/en/smallimage/logo-1680293937095.jpg){kind=logo}
/articles/billions-messages-minute/en/smallimage/LOGO-1679471830613.jpg){kind=logo}
/minibooks/jhipster-mini-book-7/en/smallimage/logo-1677849630224.jpg){kind=logo}
/presentations/java-compiler-intermediate-representation/en/smallimage/chris_seaton-s-1679038354209.jpg)
/articles/series-apache-kafka-streams/en/smallimage/apache-kafka-article-series-logo-small-1673455781546.jpg){kind=logo}
/presentations/jfr-observability/en/smallimage/Ben Evans-s-1675024642432.jpg)
/articles/secure-kafka-cluster-strimzi/en/smallimage/securing-a-kafka-cluster-in-kubernetes-using-strimzi-small-1671647644310.jpg)
/minibooks/2022-infoq-trends-reports/en/smallimage/LOGO-1672051527011.jpg){kind=logo}
/articles/graalvm-java-compilers-openjdk/en/smallimage/small-image-jdk-2023-1671096273181.jpg)
/articles/java-jvm-trends-2022/en/smallimage/InfoQ-Trends-Report-small-1670863712433.jpeg)
/articles/test-automation-ci-cd/en/smallimage/effective-test-automation-approaches-for-modern-CI-CD-pipelines-small-1685355310638.jpg)
/articles/impact-machine-learning-climate/en/smallimage/minimising-the-impact-of-machine-learning-on-our-climate-small-1685091723283.jpg)
/articles/kafka-clusters-cloudflare/en/smallimage/tales-of-Kafka-at-Cloudflare-small-1684768928637.jpg)
Community comments
Licency changes
by Luis Trigueiros,
Re: Licency changes
by Dan Tines,
Re: Licency changes
by Ivan L,
Re: Licency changes
by Michael Hunger,
Re: Licency changes
by Thomas Krafft,
Try out OrientDB
by Rohit Rai,
Licency changes
by Luis Trigueiros,
Your message is awaiting moderation. Thank you for participating in the discussion.
Does this means that it can be tried on comercial projects no string attached ?
Cheers, Oscar
Re: Licency changes
by Dan Tines,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hmm..good question about "trying". The Affero clause of the GPL is definitely strings attached though.
Re: Licency changes
by Ivan L,
Your message is awaiting moderation. Thank you for participating in the discussion.
I wish they would give us the one line answer to this as well. Last I remembered it was anything more than a million nodes required a commercial license. Otherwise, Neo4j continues to be a useless technology to me.
Re: Licency changes
by Michael Hunger,
Your message is awaiting moderation. Thank you for participating in the discussion.
It is basically the same kind of license (for the community edition) as MySQL has, so whenever you would be able to use MySQL without acquiring a commercial license you can use Neo4j.
Only the advanced and enterprise versions (with additional monitoring, HA, online backup, support, etc.) come with AGPL or commercial license nowadays.
Re: Licency changes
by Thomas Krafft,
Your message is awaiting moderation. Thank you for participating in the discussion.
When someone says a particular product is "a useless technology" just because the group producing that product has some licensing scheme that helps them generate revenues (and thereby continue to evolve and improve their product), I immediate know the person commenting is an idiot, and/or isn't working on anything really useful or important.
(1.) If it's the right tool for the job, and there are no alternatives, then saying "it's useless" shows you really don't want or need to build something. (2.) If you're building something important, chances are you will also either be paid to produce the application, or will somehow generate your own revenues from it (even if it's through banner ads on the site where the "widget" lives).
These vendors are simply saying you can start for free, and then build (and buy) as needed. It doesn't matter the type of organization building these tools, whether commercial or open source... Everyone. And I mean EVERYONE who develops these tools needs revenues to survive and continue their work. Even something as simple as travelling to an open source conference, where you have been invited to speak about your open source product, can cost a lot. If these vendors - and particularly innovative new products - don't have revenues to support their operations, the product(s) will wither on the vine and die.
That's the only point at which people like Ivan can or should truly say something is useless to them.
Try out OrientDB
by Rohit Rai,
Your message is awaiting moderation. Thank you for participating in the discussion.
A few months back I had to search a Graph DB system and I did study for a client all the systems available in the market then. Finally we decided OrientDB was the best thing.
I recommend that everyone interested in GraphDBs or DocumentDBs check it out. It is faster than Neo4j, has embedding and clustering support, a web based db management application, RESTful interface, supports Graph as well as Documents and SQL too ;)
And if you have to just go by licensing, it is licensed under the business friendly Apache License 2.0
More details here - www.orientechnologies.com/
Disclaimer - I m not related with this project in anyway, though have plans of working on it in future.