AMQP Foundation (Links)

[jsquire]

Summary

The current track two implementation delegates to an embedded copy of the track one library as its transport layer. This approach was chosen as a temporary measure to speed development and allow the track two API surface to be modeled and released for feedback more quickly. It requires translation between types in the track two context and those in track one, resulting in more allocations, higher resource use, and a less efficient communication pipeline with the Event Hubs service.

In order to provide the best experience, the track two library will be implementing its own AMQP transport layer consistent with the abstractions in place, consistent with the track two goals, and adhering to the current design principles and standards.

Scope of Work

• Create the base foundation for the AMQP link management, including types needed for creation and management of AMQP links and those responsible for managing credentials and authorization used with the links.

• Create new tests that cover the implementation surface and validate functionality.

• Update existing tests as needed to incorporate changes.

Out of Scope

• Types related to AMQP connection and session management.

• Transport abstraction types, including the AmqpEventHubClient, AmqpEventHubProducer, and AmqpEventHubConsumer

Success Criteria

• The base foundation for creating, managing, and using AMQP links as part of a transport layer specific to the track two Event Hubs client library has been implemented

• The implementation has extensive test coverage and those tests pass consistently and reliably with deterministic results.