Backwards compatibility is just not an issue in self-describing structures like JSON, Java serialization, and (dating myself) Hessian. You can add fields and you can remove fields. That's enough to allow seamless migrations.

It's only positional protocols that have this problem.

▲

dangets 7 days ago | parent | next [-]

You can remove JSON fields at the cost of breaking your clients at runtime that expect those fields. Of course the same can happen with any deserialization libraries, but protobufs at least make it more explicit - and you may also be more easily able to track down consumers using older versions.

	▲	nomel 6 days ago \| parent [-]
		For the missing case, whenever I use json, I always start with a sane default struct, then overwrite those with the externally provided values. If a field is missing, it will be handled reasonably.

▲

jimbokun 7 days ago | parent | prev [-]

At the cost of much larger payloads.

	▲	stickfigure 6 days ago \| parent [-]
		With gzip encoding... not really.