Data Subscriptions: How to Create a Data Subscription

Data subscription is a batch processing mechanism, that send the clients documents that answer a specific criteria.
In order to create a data subscription, we first need to define the criteria. The minimum is to provide the collection to which the data subscription belongs. However, the criteria can be a complex RQL-like expression defining JavaScript functions for the filtering and the projections. See a simple example:

name = await store.Subscriptions.CreateAsync<Order>();

Fore more complex usage examples see examples

Another important, but not mandatory subscription property is its name:

name = await store.Subscriptions.CreateAsync(new SubscriptionCreationOptions<Order>
{
    Name = "OrdersProcessingSubscription"                
});

In order to consume a data subscription, a subscription name is required to identify it.
By default, the server can generate a subscription name by its own, but it's also possible to pass a custom name. A dedicated name can be useful for use cases like dedicated, long running batch processing mechanisms, where it'll be more comfortable to use a human readable name in the code and even use the same name between different environments (as long as subscription creation is taken care of up front).

As stated above, upon creation, the cluster will choose a node that will be responsible for the data subscription server side processing. Once chosen, that node will be the node that will the only node to process the subscription. There is an enterprise license level feature that support subscription (and any other ongoing task) failover between nodes, but eventually, as long as the originally assigned node is online, it will be the one to process the data subscription.
Nevertheless, there is an option to manually decide the node that will be responsible for the subscription processing, it's called the MentorNode:

name = await store.Subscriptions.CreateAsync(new SubscriptionCreationOptions<Order>
{
    MentorNode = "D"
});

The mentor node receives the responsible node tag, as can be seen in the subscription topology.
Setting that node manually can help manually choosing a more fitting server from resources, client proximity or any other point of view.