TL;DR: we’re the European competitor to Palantir. We build and deploy our data intelligence platform in the World’s biggest organisations (governments, financial institutions, NGOs, industry groups, etc.).
Tech: we are centered on graph visualization with a swappable graph database backend (neo4j, neptune, memgraph, google spanner). Our stack is full typescript (nodejs, angular).
We are looking for someone who can contribute to our nodejs app while also improving our developer experience by contributing code & config to our jenkins/kubernetes/argocd/nexus stack.
Hi, would you be available to share some feedback about the process & tooling? I'm comparing tools for my needs and would love to ask you for details. I can be reached at david [at] linkurio [dot] us
As many people already commented, no one actually visualizes graphs of that size at once.
Context: I’m the CTO of a GraphViz company, I’ve been doing this for 10+ years.
Here are my recommendations:
- if you can generate a projection of your graph into millions of nodes, you might be able to get somewhere with Three.js, which is a JS library to generate WebGL graphics. The library is close enough to the metal to allow you to build something large and fast.
- if you can get the data below 1M nodes, your best shot is Ogma (spoiler: my company made it). It scales well thanks to WebGL and allows for complex interactions. It can run a graph layout on the GPU in your browser. See https://doc.linkurious.com/ogma/latest/examples/layout-force...
- If you want to keep your billions of nodes but are OK with not seeing the whole graph at once, my company builds Linkurious. It is an advanced exploration interface for a graph stored in Neo4j (or Amazon Neptune). We believe that local exploration up to 10k nodes on screen is enough, as long as you can run graph queries and full-text search queries against the whole graph with little friction. See https://doc.linkurious.com/user-manual/latest/running-querie...
I love the idea of a simplified SQL syntax for joins.
I have been working with graph databases for years now: these databases had to solve this problem from day one, because of the focus on relationships between entities.
I must point out that Neo4j was the first to propose a syntax that made traversal feel simple and natural again: the Cypher query language.
Neo4 and other industry players have spent years working on a new standard query language for graph databases that was released in April this year: GQL. GQL is the first database query language normalized by ISO since SQL, so it’s a big deal.
Graph databases aren't particularly relevant to a novel syntax for relational databases. The part of the related standard that is about relational databases (SQL/PGQ) demands that every table hold either edges or vertices, but not both [1], which is very limiting.
I think InterSystems Caché did it first. Its SQL join syntax lets you do `WHERE employee->manager->manager->name`. I'm not sure it has arbitrary recursion like you can do with graph databases, however.
We are a graph visualization company specializing in data investigations. Most of our customers are fighting financial crime.
We are a 11 years old bootstrapped French startup, we created a subsidiary in Washington DC 2 year ago to better serve the US market. We are looking for employee #2 in the US (#44 overall).
TL;DR: we’re the European competitor to Palantir. We build and deploy our data intelligence platform in the World’s biggest organisations (governments, financial institutions, NGOs, industry groups, etc.).
Tech: we are centered on graph visualization with a swappable graph database backend (neo4j, neptune, memgraph, google spanner). Our stack is full typescript (nodejs, angular).
We are looking for someone who can contribute to our nodejs app while also improving our developer experience by contributing code & config to our jenkins/kubernetes/argocd/nexus stack.
If you want to know more, please get in touch here: https://linkurious.recruitee.com/o/backend-productivity-engi...