Change data capture
Change data capture records database changes so that downstream applications can process them.
Capture changes rather than only full exports
Change data capture, or CDC, captures changes to database data for downstream processing. One possible approach reads the change log; PostgreSQL describes logical decoding for this. Other approaches may work differently.
In a fictional example, a changed product category must reach an analysis system. The technical row change does not itself explain whether the product has received business approval. CDC therefore does not replace the definition of business events. Clarify the initial dataset, deletions, schema changes and restart position. Recipients must also handle possible repeats. Capturing a change does not prove that it has been applied correctly in the target.
Sources
Related terms
- Event-driven architectureIn event-driven architecture, components report events that other components can respond to independently.
- Data consistencyData consistency means that data follows defined rules and related states do not contradict each other.
- IdempotencyAn idempotent operation has the same intended effect on system state when repeated identically as when performed once.
- Server-sent eventsServer-sent events carry text notifications from server to client over HTTP, for example about the progress of a background job.
- Entity tagAn ETag identifies a particular representation version of an HTTP resource and supports conditional reads or changes.
- Cross-Origin Resource SharingCORS controls browser access to responses across origin boundaries. It replaces neither API login nor permission checks.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.