Comparison
ConnectorvsFan-out ingestion
Connector
the sync broke because the vendor added a field, and the fix was in somebody else's code that you configure rather than edit.
A packaged piece of extraction or loading for a specific source or destination, configured rather than written. Buying rather than building these is nearly always right — the value is in the hundred edge cases of somebody's pagination and rate limiting — and the cost is that you inherit their opinions about schema, naming and incremental strategy. Every connector is a dependency with its own release notes, and treating one as infrastructure rather than as code is how a silent behaviour change reaches production.
Full entry →Fan-out ingestion
six teams each built their own connector to the same production database and the DBA noticed before anyone else did.
One captured source feeding many independent consumers instead of each consumer extracting for itself. Consolidating on a single capture is usually right — one connection to the source, one interpretation of its quirks, one place to fix a bug — and it is why a shared change feed tends to become a platform team's product. The trade is that the shared feed becomes a coupling point, so its schema and its retention become everyone's problem at once.
Full entry →