How deeply does Learn Go with Pocket-Sized Projects cover forward compatibility?

Explains the generated-interface mechanism and its alternative compiler option, but stops short of showing implementation code.

Forward compatibility

As explained in Learn Go with Pocket-Sized Projects

Forward compatibility is the ability of existing implementations to continue working when a service or data interface gains supported additions.

Forward compatibility keeps existing gRPC server implementations working when a .proto service gains a new endpoint. Generated Go code enforces this by requiring server implementations to embed a generated type. section 10.1.2

The generated server interface supports two approaches:

Require implementations to embed the generated unimplemented-server type, preserving compatibility when methods are added. section 10.1.2
Permit implementations not to implement the required server interface by setting require_unimplemented_servers=false; this option is available but not recommended. section 10.1.2

How Learn Go with Pocket-Sized Projects covers it

Cover of Learn Go with Pocket-Sized Projects

liveBook manning.com

Read Learn Go with Pocket-Sized Projects on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Machine Learning System DesignThe ability of older software or an interface version to work with new code or clients without changes.
liveBook manning.com

Kafka for ArchitectsForward compatibility is a schema compatibility policy in which consumers using an older schema can read messages produced with the new schema.
liveBook manning.com

Troubleshooting Java, Second EditionForward compatibility is the ability of an older consumer or implementation to tolerate data produced according to a newer schema.
liveBook manning.com

Apache Kafka in ActionForward compatibility is schema compatibility in which consumers using an older schema can read data written with a newer schema.

Compare how 5 books explain forward compatibility →

Related concepts

backward compatibilitykind of · Backward compatibility is the property of a changed or newer system remaining usable by existing clients and consumers of its earlier interfaces, behavior, or data.
contractused by · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
default valueuses · A default value is a predefined or automatically supplied value used when an expected input, argument, field, or configuration setting is omitted or unspecified.
breaking changeaddresses · A breaking change is a modification to an interface, behavior, format, configuration, or contract that can prevent existing consumers from working correctly without changes.

This explainer was generated by Manning's knowledge graph from the text of Learn Go with Pocket-Sized Projects. The section links point to the parts of the book it draws on.