About
A little more about John Connor Sanders.

I’m a hands-on engineer based in the Dallas–Fort Worth area with over a decade of professional experience who enjoys building software where latency, reliability, and user experience all matter.
My work tends to land where systems get critical: streaming data, observability, and AI features that need to behave like the rest of your platform.
Most of what I build sits at the intersection of:
- Streaming & data infrastructure: CDC, event pipelines, schema evolution, stateful processing
- Observability & systems tooling: turning telemetry into tools people actually use
- Productionized AI: agentic workflows, retrieval, evaluation, and guardrails
I build primarily in Rust, Go, and Python, and I enjoy taking projects from whiteboard to shipped systems.
What I care about
- Designing for failure: backpressure, retries, idempotency, schema evolution, and safe rollouts
- Clear interfaces: boring, well-documented APIs and tooling that helps teams move faster
- Measurable outcomes: performance, cost, reliability, and time-to-debug improvements
A few highlights
- Apache Arrow / Avro: helped ship
arrow-avro, a vectorized bridge between Apache Avro and Apache Arrow for Rust, and wrote the announcement post. - Streaming systems: built high-throughput gRPC/QUIC/Kafka components and CDC-friendly sinks designed for predictable performance and operational simplicity.
- Developer experience: shipped internal frameworks and open-source tooling that make it easier to build and operate streaming applications without reinventing the same concurrency and plumbing.
- Practical AI tooling: built platform primitives for secure, reliable agentic AI (LangGraph orchestration, knowledge graphs, GraphRAG, evaluation).
Stack
- Languages: Rust, Go, Python, SQL
- Streaming: Kafka, NATS, Pulsar
- Processing: Flink, Spark, Arrow, DataFusion
- Storage: Postgres, ClickHouse, Databricks
- Communication: gRPC, REST, IPC
- Infrastructure: AWS, GCP, Azure, eBPF