We spend millions turning structured information into PDFs and billions to extract the same data from a printer rendering language
171 karma · joined October 26, 2010
We spend millions turning structured information into PDFs and billions to extract the same data from a printer rendering language
Have fun
https://gist.github.com/jexp/8d991d1e543c5a576a3f1ee70132ce7...
Did you see the two blog posts that Tomaz Bratanic did on the topic?
For the ingestion: https://neo4j.com/developer-blog/global-graphrag-neo4j-langc... For the retrievers: https://neo4j.com/developer-blog/microsoft-graphrag-neo4j/
My general point on GraphRAG is that it extracts and compresses the horizontal topic-clustering across many documents and makes that available for retrieval.
And that by creating the semantic network of entities, you can use patterns in the graph structure to answer questions that rely on information coming together from different documents. Think the detectives board connecting facts with strings from many different sources.
Feel free to ping me for a deeper discussion: michael at neo4j
Very secretive all external partners were bought out. Only hundred or so people benefited in the billions per person. Including Robert Mercer of Trump campaign financing and Cambridge Analytica fame.
Very interesting but also disheartening episode about smart people only caring about getting richer.
You can also construct graphs with an llm out of text. See here. https://neo4j.com/labs/genai-ecosystem/llm-graph-builder/
https://www.prometheus-music.com/audio/eternalflame.mp3
Refrain (full lyrics): http://www.songworm.com/lyrics/songworm-parody/EternalFlame....
For God wrote in Lisp code
When he filled the leaves with green.
The fractal flowers and recursive roots:
The most lovely hack I’ve seen.
And when I ponder snowflakes, never finding two the same,
I know God likes a language with its own four-letter name.
They operated in the early 2000s and went bankrupt.
They construction dome is as high as the Statue of Liberty and as long as the Eiffel Tower. Now used as indoor tropical resort.
The renewable energy transition was blocked and delayed by the same Merkel govt. Germany was once leading in wind and PV energy and all those industries were destroyed and almost 100k jobs lost. 60bn subsidies per year go to fossil fuel companies including coal mining and burning. Often under the disguise of job retention. All through industrial lobbying and strong unions in the fossil fuel industries.
It even made it on LifeHacker back then: https://lifehacker.com/track-your-time-with-lego-bricks-3997...
The article is only on the internet archive these days https://web.archive.org/web/20081206084136/http://jexp.de/bl...
MATCH (e:Employee) RETURN e { .* } as employee;
MATCH (e:Employee) RETURN collect(e { .* }) as employees;
MATCH (e:Employee)-[:IN]->(d:Department) WITH d, collect(e {.*}) as employees
When I started back then in 2016 with it, it was pretty cool how directly graphql mapped to the graph model in the db.
And changing the tagline on relational database from "Relational databases: a software engineering fail" to "Relational databases: engineering success is not always the best software engineering fit"
https://dgraph.io/blog/post/graphdb-for-your-next-app/
Fortunately internet archive still has the previous version, that the comments here were discussing. https://web.archive.org/web/20200709192510/https://dgraph.io...
Every database benefits from having the _hot_ dataset in memory, so that's the same with Neo4j.
2011 was many years ago, since then the memory management has been completely rewritten. You very probably wouldn't use the Neo4j Browser in production as it is meant to be a developer tool. Usually, you would build an app that uses the drivers to connect to the db.
In the graph databases book (graphdatabases.com) there is a chapter on the internal architecture of Neo4j.
"Claiming ACID" what is ambiguous about that? Transaction support with different serialization levels, like other databases that offer it.
And Neo4j originally started b/c RDBMS was not able to execute the complex deep traversals needed in real time. Dedicated storage & query engine for graphs allow you to run statements quickly that would otherwise take too long to execute.
Regarding the data model, the property-graph model is much closer to the object model but with richer relationships, it doesn't suffer from the object-rdbms impedance mismatch and is better suited to express real-world domains & scenarios. It also represents semantic relevant relationships as first class citizens in the database, allowing for proper information representation and much faster retrieval.
Disclaimer: I work with/for Neo4j, for 8+ years and still love it.
The most fun things are in-query dataflow which allows you to pass information from one query part to the next (projected, aggregated, ordered etc).
And the really cool collection and map functions, so you save a lot of roundtrips between client and server.
I mean expressing this is easy and the execution is also straightforward, e.g. in Neo4j:
MATCH (lunch:Lunch)<-[:PART_OF]-(drink:Drink) RETURN lunch, COUNT(drink) ORDER BY lunch.delivery_date, lunch.total_price
this would be a more efficient variant:
MATCH (lunch:Lunch) RETURN lunch, size((lunch)<-[:PART_OF]-()) as drinks ORDER BY lunch.delivery_date, lunch.total_price
So I don't agree with the statement, that everything which is not recursive is better served by and RDBMS.
There is more than one use-case for your data most use-cases in real applications are more than mildly complex.
And GraphDBs might not be much faster on those types of queries but they are also not tremendously slower.
We have sound investment and revenue, growing list of large and small customers and a super active community, which I'm really proud of. All of that while driving a lot of cool development in the product. Could't be a better time.
I'd be happy if more graph databases show up that actually drive the graph database space forward than having petty fights between each other.
Disclaimer, I work for Neo as you can tell but happy to discuss concrete details any time.