Backwards compatibility future plans

Thank you for this great library. We have integrated CloudEvents in our system already and would like to start using this library too.

There were some breaking changes between v0.1 and v0.2 in the CloudEvents specs and I see that at the moment cloudevents/sdk-java is backwards compatible. (example)

But since these are versions before the major version v1.0, could you please tell me if you intend to always keep backwards compatibility in the future for any new versions of CloudEvents specs (for any future breaking changes)?

It is important for us to be able to gradually update our events with every new CloudEvent version. This results in a Kafka topic with multiple versions of CloudEvents. To avoid creating custom adapters, it would be great to only rely on the cloudevents/sdk-java library no matter which version of CloudEvents we use.

Thanks, Cristian

[slinkydeveloper]

IMO all major versions should be backwards compatible. Upgrading services to publish/consume new version of the CloudEvents is done one stream at a time. In a distributed system it is almost impossible to update all producers and consumers at the same time.

I’m sorry, I explained myself badly. Both sdk 1.x and 2.x supports cloudevents spec versions 0.3 and 1.0, so they should be able to talk each other, if that’s what you mean. APIs however will be different, in order to simplify the usage of the sdk and this unfortunately requires breaking the Java APIs

[matzew]

I like the idea of deprecation.

and perhaps add some function to go from 0.x -> 1.0 as a conversion hook