A few posts ago we described connectors as the edges of the dataflow graph, the points where a typed record crosses out of one process and into the world. link_to streams a record out, link_from brings one in. Same builder, same buffers, op...
I pasted a URL into Claude Desktop, asked "what's the temperature in Munich right now?" and got a live answer streamed from a sensor running on a microcontroller. No RAG. No vector DB. No tool-calling glue I had to write. The agent was read...
Most connectors carry data. A sensor publishes a reading. A dashboard receives it. If the reading arrives a second late, the chart is a second late. Telemetry is patient. Some connectors carry consequence. A link_from on a SingleLatest buff...
A record produced on a microcontroller and consumed in a browser is still the same record. Same SchemaType. Same key. Same contract. That is exactly why a new question appears the moment you cross runtimes: when the same record exists on bo...
A reactive pipeline moves records from a source through transforms to a tap. It's a complete story inside the runtime. But records don't appear from nowhere and they rarely stop where they're produced. Something brought them in. Something w...
The Data Graph Is Just a Map In "The Next Era of Software Architecture Is Data-First", we argued that the data model is the architecture. Records, buffers and producer/consumer relationships form a graph. But declaring a graph is not the sa...
Software architecture has always been organized around behavior. You design services, write functions, define APIs. Data is a consequence — something that gets passed around, stored and analyzed. Observability is instrumented on top. Experi...
The Hidden Cost of Distribution Schema drift is a common issue while working on distributed systems. A lot of solutions like schema registries and serialization frameworks gained significant importance, but all of them feel like workarounds...