backward compatibility

The property that a new version of an interface still works for clients written against the old one.

In more detail

Additive changes, such as a new optional field or option, are usually backward compatible, but only if clients ignore what they do not recognise and old meanings stay the same. Under semantic versioning, compatible changes can ship in minor versions, while anything that could break a consumer needs a major version.

Example

Schema registry BACKWARD level: consumers on the new schema can read old records, so upgrade consumers first.

Related terms

Taught in

References

Certification courses