Microsoft Bond架构演变最佳实践(Microsoft Bond schema evolution best practices)

 Microsoft Bond是否有一些关于模式如何随时间演变的最佳实践？ 我想确保我们遵循最佳实践，以便我们具有双向兼容性（即允许我们的Bond类型将旧版本发展到当前版本，以及向后兼容性允许从较新版本转换回旧版本）。 我没有在文档中具体说明这一点（例如https://microsoft.github.io/bond/manual/bond_cs.html或https://microsoft.github.io/bond/manual/compiler.html#idl -syntax ），尽管其他序列化框架（例如Avro）在其文档中明确详细说明了这一点。 
 
 对于它的价值，我们用.NET编写（C＃/ F＃）并打算最初使用CompactBinaryWriter和CompactBinaryReader格式。 
 
 例如，我想象一下这些方面的一些指导： 
 
 
 
 字段名称可以随着时间的推移而变化，因为字段序数用于字段解析，而不是直接名称（SimpleJSON除外）。 我相信这是真的，是吗？ 
 
 
 添加新的“必需”字段需要您为该字段指定默认值 
 
 
 如果旧版本分配了默认值，则删除较新版本中的字段是可以的 
 
 
 那么改变一个领域的类型呢？ 例如，字段是否可以从版本1中的字符串字段更改为版本2中的int64？ 它可以从字符串更改为自定义联合（具有可选字段的自定义类型）吗？ 
 
 
 还有其他建议吗？ 
 
 
 谢谢！ 
 
 如果有这种类型的Microsoft Bond问题有任何活跃的论坛社区，我也会感兴趣，我无法找到一个...... 

Does Microsoft Bond have some best practices on how schemas evolve over time? I want to make certain we follow best practices such that we have 2 way compatibility (i.e. allowing our Bond types to evolve older versions to the current version, as well as backward compatibility allowing conversion from a newer version back to an older version). I don't see this addressed specifically in the documentation (e.g. https://microsoft.github.io/bond/manual/bond_cs.html nor https://microsoft.github.io/bond/manual/compiler.html#idl-syntax ), though other serialization frameworks such as Avro have this explicitly detailed in their documentation.
 
For what it's worth, we are writing in .NET (C#/F#) and intend to use the CompactBinaryWriter and CompactBinaryReader formats initially.
 
For example, I imagine some guidance along these lines:
 
 
 
names of fields can change over time since the field ordinals are used for field resolution, not the names directly (except in SimpleJSON). I believe this true, is it?
 
 
adding a new "required" field requires you give the field a default value
 
 
removing a field in a newer version is okay, provided older versions had a default value assigned
 
 
what about changing the type of a field? For example, can a field change from an string field in version 1 to a int64 in version 2? Can it change from a string to a custom union (custom type with optional fields)?
 
 
any other recommendations?
 
 
Thank you!
 
would also be interested if there is any active forum community for this type of Microsoft Bond question, i wasn't able to find one...

原文：https://stackoverflow.com/questions/41860787