Comparison
Anti-corruption layervsConnector
Anti-corruption layer
you wrap the legacy system's awkward model in a translation layer so its concepts do not leak into your new code.
A translation boundary between your domain model and an external or legacy one. It keeps a foreign model's naming, quirks and constraints from spreading through your codebase. It costs an extra mapping layer, and it is what you wish you had built the first time a third-party field name ended up in your database.
Full entry →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 →