Silverback 2 Release Notes
2.2.0
Released on 2020-07-08
What's New
- Allow custom outbound routers to be registered as scoped or transient (instead of singleton only)
2.1.2
Released on 2020-06-18
Fixes
- Fix delay in Retry policy [#97]
2.1.1
Released on 2020-05-14
What's New
- Add support for multiple message brokers (Kafka and RabbitMQ) in the same application (see Connecting to a Message Broker)
- Add end-to-end message encryption (see Encrypt Produced Messages and Decrypt Consumed Messages)
- Add dynamic custom routing of outbound messages (see Producing Messages)
- Improve support for message headers (see Setting Headers and Reading Headers)
- Add support for binary files (see Serializing the Produced Messages and Deserializing the Consumed Messages)
- Improve message identifier handling: the IIntegrationMessage is not required to have an
Idproperty anymore (thex-message-idheader will still be generated and if the property exists will continue to be automatically initialized) x-first-chunk-offsetheader added by default (see Default Headers)- Deserialize KafkaStasticsEvent JSON and provided its content as an object (in addition to the raw JSON)
- Add support for Apache Avro and schema registry (see Serializing the Produced Messages)
- Upgrade to Confluent.Kafka 1.4.2
- Add consumer
PrefetchSizeandPrefetchCountsettings toRabbitConsumerEndpoint - Add
AcknowledgeEachto theRabbitConsumerEndpointto define the number of message processed before sending the acknowledgment to the server - Upgrade to RabbitMQ.Client 6.0.0
- Improve message type resolution performance and reliability in JsonMessageSerializer
- Add
LogWithLevelmethod to SkipMessageErrorPolicy to specify the desired level for the "Message skipped" log entry (the default is now increased toError)
Breaking Changes
These changes shouldn't affect you unless you built your own IBroker implementation or are interacting at low-level with the IBroker (this is why has been decided to still mark this as a minor release):
- The
IBrokerinterface andBrokerabstract base class have been modified to explicitly declare which endpoint type is being handled by the broker implementation - The IMessageSerializer interfaces has been changed
- The IConsumerBehavior and IProducerBehavior interfaces have been changed
- Changed the parameters order in some less used overloads in the IBrokerOptionBuilder
Announced Breaking Changes
These aren't real breaking changes but some methods have been marked as deprecated and will be removed in one of the next major releases:
WithConnectionTo<>,WithConnectionToKafkaandWithConnectionToRabbitMQare deprecated (they will still be supported in this version), please use the newWithConnectionToMessageBrokerandAddKafka/AddRabbitmethods (see Connecting to a Message Broker)
2.0.0
Released on 2020-03-10
What's New
- Create Silverback.Integration.RabbitMQ package to connect Silverback with RabbitMQ
- Enable subscription of messages with an empty body (you must subscribe to the IInboundEnvelope) [#61]
- Add hook to manually set the Kafka partition start offset when a partition is assigned to the consumer (see Broker Callbacks) [#57]
- Support for multiple consumer groups running in the same process [#59]
- Publish KafkaStatisticsEvent also from the KafkaProducer (previously done in KafkaConsumer only)
- Several reliability and performance related improvements
Breaking Changes
- The
IBroker, IProducer and IConsumer interfaces have been slightly modified (it shouldn't affect you unless you built your ownIBrokerimplementation) - Many interfaces (such as IBehavior) and delegates have been slightly modified to pass around an IReadOnlyCollection
instead of an IEnumerable , to avoid the possible issues related to multiple enumeration of an IEnumerable - The IMessageKeyProvider interface has been renamed to IMessageIdProvider to prevent to be mistaken with the Kafka Key or Rabbit's Routing Key
- IInboundMessage/IOutboundMessage (plus all the related types) have been renamed to IInboundEnvelope/IOutboundEnvelope and the property containing the actual message has been renamed from
ContenttoMessage - The
MustUnwrapoption has been removed from the inbound connector configuration (messages are unwrapped by default)