Insights on Graphs and Tools

We notice a pattern in a diverse collection of software tools that help humans wrestle with difficult problem spaces. They have a few ingredients in common including connected graphs, an endless stream of changes, and groups of people trying to make it easier for other groups of people to make sense of their tangled messes.

Ward on Guiding Emergent Structure. He built a graph database to query and visualize the relationships between sociotechnical components of an internet-scale distributed system. For the past few years, he's been experimenting to bring similar tools and approaches to federated wiki. lineup

Netflix Engineering bragging about visualizing real-time distributed tracing data from a sprawling microservices architecture. Designing the machine to leverage and empower human perception. 2015. page

Steampipe brought to our attention by Jon Udell. Clever customization of PostgreSQL for consuming and composing APIs. This introductory page explains the benefits of reducing the context switching to empower a journey from exploration to understanding to sharing and explaining to others. 2021. page

Netflix Engineering bragging about tools to search a sprawling federated GraphQL API. Getting all the APIs into a federated GraphQL space is the beginning of the problem. Once you have All The Things in one place, you discover there is too much for anyone to understand. Immediately you need to filter, sift, rearrange, and join those things into smaller pieces to make sense of any of it. 2022. page

Netflix Engineering bragging about a SQL-like DSL for consuming and composing streams of event data. If you are going to search a pile of federated data, you need to build indexes. The graph can help organize the indexes. 2023. page