What are the technical implications of choosing asynchronous or synchronous billing cycle? When using the Commerce License Billing module the "/admin/commerce/config/license/billing-cycle-types/manage/monthly" page clearly states:


  Asynchronous
  
  Determines whether the billing cycle starts at the time
  of purchase, instead of starting at the beginning of the calendar
  period.  For an order placed on Jan 5th, a monthly synchronous billing
  cycle would start on Jan 1st 00:00 and end on Jan 31st 23:59:59, 
  while a monthly asynchronous billing cycle would start at the time of
  purchase (Jan 5th) and end a month later (Feb 5th).


I wonder what are the technical implications of choosing asynchronous or synchronous billing cycles. I mean if I go with synchronous billing period will all the recurring services be renewed on 1st of each month at the same time? Won't that make it difficult for cron?

Synchronous billing cycle seems very convenient and more appealing to the end-customers, however my main concern is that Drupal cron might stack in posterity with growing number of orders for the recurring services in the system.

Could anybody elaborate on this to confirm or mitigate my concern?
The "implications" are that it mimics how you want to charge your customer for access. If you want to provide a revolving 30-day access to some content, an asynchronous billing cycle might make the most sense. Whereas if you're charging for a service and want everyone to have the same billing cycle, then you'd end up prorating the first month to get to the first point of your billing cycle.



At a technical level, cron should be running in daemon mode (or at least every 5-10 minutes) since your license provisioning requires it. You shouldn't have to do anything different.