ohhh... I wait with anticipation of the next article, it's like Serial all over again, maybe I'll start a post so we can discussion this post and come up with theories about what the next one will contain ... a post about a post!

Do you feel it's better to have the Nintex Service hosted closer to you or closer to datacentre where SharePoint is located.

Example is SharePoint data located in East Asia, Microsoft gave option to move to Australia but said what would impact cache efficiencies as data would be locked to Aus data centre, with users in all regions (primarily US and AUS).

Other than Forms which are rendered to the user, the workflow runs on it's own schedule (especially in O365 ) - so would there be any noticeable improvement, making the effort worthwhile?

Well, there are three things to consider: forms-UI (designer as well as runtime), workflow-designer and workflow-runtime.

The forms-designer and runtime are mostly interacting with the user - so you would want to have this closer to the user. Forms does interact to some degree with Sharepoint as well, as it will write data to Sharepoint or read data from Sharepoint-lists (eg.g lookup-fields).

The workflow-designer is also interacting with the user, so this should also be rather to close to the user - obvious.

The workflow-runtime is only interacting with Sharepoint. Since Nintex offers more than the out-of-the-box actions offered by SharePoint-Designer these additional actions are hosted by Nintex. The get called from the workflow via the "call webservice-action" provided by the workflow-manager. In turn those actions might access Sharepoint using the client-side-object-model. So there are some heavy ties between the workflow-manager, the Nintex-infrastructure and Sharepoint. So you might want to keep Sharepoint and Nintex as close as possible to avoid any unnecessary delays because of latency and such.

In my case this was an easy call - all our users are located in europe, our Sharepoint tenant is located in europa, so me moved our Nintex tenant to europe as well.

 if only ever case was that straight forwards, I appreciate the response!

Hi,

what do you actually mean by "data would be locked to Aus data centre"? Currently your data lives in East-Asia, and you have to travel vom US and AUS to East-Asia to access you data. If you would move your tenant to AUS, then at least the access from AUS should be more efficient. I don't know if the access from the US would be affected - would be interessting to know if it would be more efficient to access East-Asia vs AUS from the US.

You might wan to have a look at Azure Storage Latency Test - Azure Speed Test. Although this is not directly Office365 - I think this will still give a clue on what datacenter would give you the best performance. I would check the speed from AUS as well as the US and then measure for e.g. datacenters in East-Asia, AUS and the US to see what would be the best location for your tenant.

Then I would consider moving O365 as well as Nintex to one datacenter.

Thanks for that link, I will certainly look into it further.

With the data centers, as we were using O365 before the AUS data center came online we were provisioned in East Asia, Microsoft gave the option to move tenant to Australia which expired last year, but the stipulation was if we moved Microsoft would not be able to optimise out content to be access from other regions as we were effectively asking for

data sovereignty in aus, and as such we didn't move as we are a global company and want the best experience for all users.

With over 800+ workflows it's a big task to republish all of those. I'm not sure how workflow that are already running are handled in the move. Certainly will continue to consider for our scenario.

Well - the re-publish is definitely a challenge. That's why I wrote this little series, although you'll still need to re-publish the workflows.

As for running workflows: they will continue to call whichever data-center was current at the time the workflow was started. Only new instances will use the new data-center, since this binding is changed during the publishing.

As far as the actual "move" operation is concerned, this shouldn't really affect the running workflows, as the workflow itself is online handled by the workflow-manager, which is part of Office365. All this Nintex tenant-hosting is about the designer and the services offered by Nintex to extend the capabilities.

Another think you might have to consider when moving your tenant: you'll have to re-publish all forms that use a mobile-layout. I didn't cover this in this series (as I so far only focused on workflows, since I don't have any production forms which use mobile-layouts).

BTW: I published