Main content
Routes · Through a pipeline
Ingestion
Getting records out of systems you do not own, exactly as often as they changed.
- 1Data MovementHow do records cross between two systems that have independent rates, independent availability and independent lifetimes, and what are you willing to lose when the assumption underneath the crossing breaks?
- 2Change Data Capture & Incremental ProcessingWhat does it cost to know what changed, and is that cheaper than not needing to know?
- 3Schema Management & EvolutionWhat happens when the shape of your data changes on its own schedule, and nobody can change the readers, the writers and the old data at the same moment?
- 4Fault Tolerance & Delivery SemanticsWhat is the cheapest thing that can be safely done twice?
- 5Time & Temporal SemanticsWhen am I allowed to act on data that may still be incomplete, and what do I owe the reader if I was wrong?