Azure Notification Hubs APIs - Benfits of DirectSend/DirectBatchSend vs. Registration/Notification/Tags styles
<p>We're planning on implementing a server-side notification mechanism that pushes out to iOS and Android via ANH.  We will have no code footprint on our mobile clients, short of a call to our server API for "registration".  In this way our approach is looking similar to this <a href="https://msdn.microsoft.com/en-us/library/azure/jj927170.aspx#Anchor_1" rel="nofollow">MSDN discussion</a>.</p>

<p>I also see the alternate, more <a href="https://msdn.microsoft.com/en-us/library/azure/mt608572.aspx" rel="nofollow">bare-bones</a>, approach noted on MSDN.</p>

<p>Is it fair to conclude that the two approaches will have similar performance on the 'send' side?  </p>

<p>It appears the main difference is this:</p>

<ul>
<li>The former approach has already done the work of integrating with the Task and Async mechanism, presenting a callable C# mechanism that has taken on more of the RESTful API layer, </li>
<li>The DirectBatch/Send API is just that -- the raw RESTful API for you to use as you see fit.</li>
</ul>