anchor.diff:  == Further Changes
   
   Let's take a look at some more features new in Debezium 1.9.
  -First, Debezium Server has now a sink adaptor for HTTP,
  +First, Debezium Server now includes a sink adaptor for HTTP,
   which means it can be used as a "native" event source for Knative Serving,
   without the need for sending messages through a message broker like Apache Kafka first.
   
  
positive.code: the database history for connectors like the MySQL one can now be stored in Redis,
  also offsets which can be stored there now.
  But they didn't stop there: for instance, Debezium Server now supports custom configuration providers,
  as already known in Kafka Connect.
  
  Going forward, the Redis Labs teams is planning on further cool improvements to Debezium at large,
  such as better retrying logic.
  Looking forward to those!
  
  
negative.code: and you are very much invited to join the https://groups.google.com/g/debezium/[discussion] either on the mailing list or on the https://issues.redhat.com/browse/DBZ-3899[DBZ-3899] issue in Jira.
  Note that while we want to take the opportunity to clean up some odditities which have accumulated over time,
  backwards compatibility will be key concern as always, and we'll try to minimize the impact on existing users as much as possible.
  But as you would expect it from a new major release, upgrading may take a slightly larger effort in comparison to the usual minor releases.
  In terms of a timeline, due to the size and number of planned changes, we're going to deviate from the usual quarterly release cadence and instead reserve two quarters for working on Debezium 2.0,
  i.e. you can look forward to that release at the end of September.
  In the meantime, there will be bugfix releases of the 1.9 version, as needed per reported bugs.
  