Proposal for Event Processor in JS

EventProcessor-JS-proposal.js

// User class extending the base class provided by the library
class SamplePartitionProcessor extends PartitionProcessor {
    async processEvents(events) { console.log(events);}
    async processError(error) { console.log(error); }
    async initialize() { console.log(`Started processing partition: ${this.partitionId}`); }
    async close(reason) { console.log(`Stopped processing partition: ${this.partitionId} for reason ${reason}`); }
}

// 3 constructor overloads similar to EventHubClient, extra arguments are consumerGroupName, and PartitionProcessor
// Options are not shown, but are similar to what EventHubClientOptions support + max batch size, max wait time per batch
myProcessor = new EventProcessor(connectionstring, consumerGroupName, SamplePartitionProcessor);
myProcessor = new EventProcessor(connectionstring, eventhubName, consumerGroupName, SamplePartitionProcessor);
myProcessor = new EventProcessor(fullyQualifiedNamespace, eventhubName, credentials, consumerGroupName, SamplePartitionProcessor);

// And/Or use the EventHubClient as we have proof that adding more connections doesnt help JS much
myProcessor = new EventProcessor(eventHubclient, consumerGroupName, SamplePartitionProcessor)

// Start without partition manager, user attempt to checkpoint will fail
myProcessor.start();

// Start without partition manager, but with top level error handler, user attempt to checkpoint will fail
myProcessor.start(errorHandler)

// Start by passing partition manager that uses blobs for checkpointing & load balancing
containerClient = new ContainerClient("storage-connection-string", "container-name");
myPartitionManager = new BlobPartitionManager(containerClient);
myProcessor.start(myPartitionManager);

// Start by passing error handler & partition manager that uses blobs for checkpointing & load balancing
myProcessor.start(myPartitionManager, errorHandler);

// Stop the event processor
myProcessor.stop();

@KrzysztofCwalina

I don't like that method receive returns an object that needs to be started, ... . Receive is a verb and so it should actually do something.

The proposed API does not require user to "start" anything. The very act of calling receive on the client starts the receiving of events

I don't like that consumer.receive takes multiple callbacks. If we use callbacks, it would be better to have them be properties.

That is a JS specific API that is under separate review. I have updated the above proposal to replace it with a receiveBatch() call that returns a promise that resolves to an array of events