Messaging - Event Hubs for Java (January-June 2021)

[AlexGhiondea]

Azure Event Hubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers. This lets you process and analyze the massive amounts of data produced by your connected devices and applications.

The azure-messaging-eventhubs package provides the SDK for Java developers to write applications that use Azure Event Hubs. Version 5 of this package follows the latest guidelines for writing Java SDKs for Azure services with the goal of being a client library that is developer-friendly, idiomatic to the Java ecosystem, and as consistent across different languages and platforms as possible.

This issue tracks the work we have planned for this package for the duration of January - June 2021

New features:

• Provide custom hostname support for users who run their applications in a private network that lacks access to public endpoints and require the ability to specify a custom host name to ensure they route through the proper intermediary for the connection to be made.
• Connection string parser so that users can parse the namespace and event hub name from the connection string in case they chose to use the constructor overload that supports AAD
• Idempotent Producer in preview to support the feature of server side deduplication
  - [ ] Receiver redirect to support the service side redirects where the main benefit is that it allows a more direct connection to the host which should reduce latency.
• Support for SharedKeyCredential and SASCredential to allow rotation of Shared keys and SAS tokens which is not possible when using connection strings
• Support reading the underlying AMQP message on an Event Data.
• Support the use of BinaryData in EventData
• Expose APIs in core-amqp that will allow creating an AMQP receiver link to help create a sample that shows how to get the connection string for the built in Event Hub endpoint of an Iot Hub instance

General improvements:

• Review and improve logging story
• Review and improve tracing story
• Fix incoming customer reported issues
• Build Trouble Shooting Guides

Testing improvements:

• Improve stress test infrastructure, consider containerizing the tests
• Add perf tests that are run before every update to catch regressions
• Fix flaky tests
• Try out rhea to set up a mock server that can emulate Event Hubs in our tests. The JS team will be trying this out first.

Documentation

• Consider having counterparts to the samples in https://github.com/azure/azure-event-hubs that use azure-eventhubs