> That’s an important point. The collaboration model is more complex in GIS because it’s not just documents (maps and map projects) but the underlying data is coming from databases that are independently editable.

Theres other complexity too, like 'how to avoid silent failures in ArcGIS Pro and Hosting Server'.

Case in point: say you use amazon RDS. URL for that object is name.customerID.environment.amazonrds.com . Its a long URL. Now you go into hostingServer/ArcGIS/manager and go set this as a data source. You can validate the data source and everything's fine...

Until your analysts add projects in RDS and go past some secret legacy arbitrary length of DNS+path. And if you do? Things will silently break, data won't come into ArcGIS Pro right. Anomalous errors.

Now, if you change the RDS DNS name to an IP address, all those problems go away! Everything's fixed, analysts are happy, and none are the wiser.

Until, Amazon does maintenance on your RDS, changing your IP address. Then, your environment then breaks for no good reason, and you have to be keenly aware to go to server manager and MANUALLY rerun data store check.

And no, ArcGIS monitor can't do this.

And... Dont even start me on 80070035. That "premium" support ticket was rotting for 5 weeks, until I ran into an engineer on LinkedIN, who solved it in 30 seconds.