How to mentioned PartitionKey -- ConsumerGroup binding in EventHub, Azure -

i want integrate application through event hub multiple type of devices mobile app, different type of embedded system etc. different type of senders sending data in specific format , need specific handler well. shown below

mobile app (partition key “mobileapp”) = consumer group 1 embedded system 1 (partition key “embedded1”) =  consumer group 2 embedded system 2 (partition key “embedded2”) =  consumer group 2 

so can please tell me how should specify above binding in event hub implementation each type of message should handle particular consumer group?

normally see on receiver side default consumer group name mentioned. can during eventprocessorhost implementation can create new consumergroup method namespacemanager.createconsumergroupifnotexists(ehd.path, consumergroupname). not able understand how make sure messages associate particular partition key handling associate consumer group. should mentioned partitionkey, consumergroup binding.

in short, there no straight forward way specify partitionkey consumergroup binding.

here's why:

eventhubs high throughput durable stream offers stream-level semantics. put, imagine equivalent simple in-memory stream cursor on stream (using eventhubclient receivebyoffset or receivebytimestamp api's) , call readnext() next events. if want such stream hold events @ huge scale - 1 day's worth of data - , want persistent (cases if app, processing stream, crashes, don't want loose data) - that's when need eventhub.

now coming question, feature - filter events based on property on event - not stream level operation - event level operation.

typical approach implement - pull events eventhubs (the event stream) , have worker process (in case, filter partitionkey) events , push them individual queues (or partition data push group of devices topics , have subscriptions pulls data off - filters).

now, first question answer before decide on using eventhubs : foresee scale requirements offered eventhubs vs "directly using servicebus topics" provides exact semantics looking for.

hth! sree