Software Best Practices for Data Pipelines: Form Energy's Multi-Day Storage R&D Pipeline 🌳
summary
Form Energy runs 100-hour iron-air batteries research with thousands of experiments and needs pipelines that deliver fresh correct data each morning. The stack uses Dagster, CircleCI regression tests, AWS EKS containers, infrastructure-as-code and standard Python logging, and adds structured events and tracing via OpenTelemetry/Honeycomb. Concrete wins include alerting on a Cron job that dropped daily rows to zero, spotting an API creeping toward a 30s Lambda timeout, and flame-graph traces that link pod errors to experiment IDs.
AI-written summary · about
chapters (10)
- 0:00Introduction to Form Energy
- 2:10Form Energy’s Battery R&D
- 3:32Data Pipeline Challenges
- 5:18Quality Gaps in Pipelines
- 7:23Pipeline Quality Stack
- 10:51Structured Events and Tracing
- 15:11OpenTelemetry in Pipelines
- 18:42Open-Source Contribution
- 19:50Reliable Data Delivery
- 20:33Q&A
related talks
30mDesigning Resilient Data Pipelines
34mData pipelines powered by Open source and fun
43mData Pipelines à la Mode
45mResilient Predictive Data Pipelines
29mDagster: a Framework for Data Processing Applications
19mBuilding Stateful Streaming Pipelines
45mDefining data pipelines
47mOpen Source for Energy Transition via Data Management - Eyes on a Major Prize
