Section 3 of 3 · 14 lessons

Graph Databases

A pump fails. Which equipment depends on it, and which inspection tells us why that connection matters? The answer follows relationships across the records. We will give those relationships a place in the database, learn to query their patterns, and build traversals with Botie. As the graph grows, we will handle repeated routes, conflicting identities and evidence that has gone out of date.

0 of 14 finished

Representing Connected Records

A failed pump can affect equipment connected to it. Give each asset an identity, name the relationships between assets, and decide what information belongs on the connection itself.

  1. 01Which Equipment Depends on This Supply?Represent equipment and its directed dependencies as nodes and relationships before choosing how to query the connections.
    Build with Botie →Read the lesson
  2. 02Are These Two Pumps Actually the Same Pump?Separate durable identity from names, qualify external IDs by their source and detect collisions before merging records.
    Build with Botie →Read the lesson

Asking Questions of a Graph

The team needs inspections of equipment served by a particular pump. Describe that connected pattern, follow its matches, and keep track of what happens when an expected relationship is absent.

  1. 03Who Inspected This Pump?Match a connected pattern and preserve variable bindings across steps instead of accidentally combining unrelated records.
    Build with Botie →Read the lesson
  2. 04How Many Inspections Were Actually Completed?Filter bound properties and aggregate at the intended grain, distinguishing paths, relationships and distinct inspection identities.
    Build with Botie →Read the lesson
  3. 05Keep the Pumps That Have No Completed InspectionUse optional graph patterns without losing the starting population or mistaking an unmatched placeholder for a real inspection.
    Build with Botie →Read the lesson

Following Connections

A fault may reach equipment several connections away. Explore the network without circling forever, then decide whether we need every reachable asset or a particular route.

  1. 06Follow a Dependency Without Following It ForeverSeparate reachability from path enumeration, handle cycles explicitly and interpret bounded traversal results without promising complete discovery.
    Build with Botie →Read the lesson
  2. 07The Route with Fewer Stops Takes LongerDistinguish minimum-hop paths from minimum-cost paths and implement Dijkstra’s nonnegative-cost frontier with explicit unreachable and tie semantics.
    Build with Botie →Read the lesson

Maintaining a Graph

Imports, corrections and concurrent work can change the network we are querying. Preserve identities and valid relationships while making queries practical on a larger graph.

  1. 08Which Rules Must Every Asset Write Preserve?Separate key presence, uniqueness and lookup performance, then audit existing data before installing graph constraints.
    Build with Botie →Read the lesson
  2. 09The Graph Changed While the Approval Was WaitingTreat approvals and snapshot checks as preparation, then use authorised, parameterised transactions with explicit conflict and retry behaviour.
    Build with Botie →Read the lesson
  3. 10A Replayed Import Must Not Create Another RelationshipStage graph imports by stable identity, distinguish exact replays from conflicts and preserve rejected records instead of silently losing relationships.
    Build with Botie →Read the lesson
  4. 11Why Did One More Hop Make the Query So Expensive?Read query plans, reason about candidate expansion and compare access paths without confusing a toy operation count with measured database performance.
    Build with Botie →Read the lesson

Shared Meaning and Evidence

Two systems can use different names for the same equipment, or disagree about a connection. Make the meaning of a statement explicit and retain the evidence behind it.

  1. 12Can Two Teams Describe the Same Resource?Distinguish resource identifiers from literals, read RDF statements and build SPARQL patterns without confusing RDF with the property-graph model.
    Build with Botie →Read the lesson
  2. 13Where Did This Maintenance Claim Come From?Represent claims and their sources, retain contradictions and apply explicit time boundaries before using graph evidence.
    Build with Botie →Read the lesson

Graphs in ML Systems

A model or an agent may need the equipment surrounding a fault, together with the documents that explain those connections. Retrieve that context with boundaries on time, access and relevance.

  1. 14Which Connected Records Can the Assistant Use?Build bounded graph retrieval with access and time boundaries, then preserve evidence and measure whether the added context actually helps.
    Build with Botie →Read the lesson