Love this soundbite. I did not know this and will totally use it to sound smart at dinner parties.
On a somewhat related note, the reason why Peugeot cars have a "0" in their model numbers (e.g. 208, 308, 408, etc.) goes back to the days before electric ignition, and when you still needed a crank to start the engine. The model number was in the middle of the grill, and the crank would go into the "0".
I'm one of the people behind Fix Inventory. What scares a lot of developers away from graph-based tools is the graph query language. It has a steep learning curve, and unless you write queries every day, it's really cumbersome to learn.
We simplified that with our own search syntax that has all the benefits of the graph, but simplified a few concepts like graph traversal.
I've built analytics products, and the good thing about dashboards is that there's budget for them. People like eye-candy, and are willing to pay for it. I like how you picked Postgres as your initial database, because I think it's still the #1 databases for analyics (even though it's OLTP) that no one talks about.
The three products where I think you may want to write short comparison pages are:
- Rill
- Preset
- Metabase
And I'd take a hard look at ClickHouse as your next database. They're missing a dashboard partner. And I think they're users are much more engineering-centric and therefore a good fit for you than the analytics crowd around Snowflake.
On a somewhat related note, the reason why Peugeot cars have a "0" in their model numbers (e.g. 208, 308, 408, etc.) goes back to the days before electric ignition, and when you still needed a crank to start the engine. The model number was in the middle of the grill, and the crank would go into the "0".