We have implemented AlwaysOn Availability Groups (AG) on a 3-node cluster, consisting of 2 subnets: primary and DR.
2 nodes on the primary site host a failover-cluster instance (FCI) in an active-passive configuration.
The 3rd node on the DR hosts a standalone SQL instance, serving as a secondary AG replica in async-commit mode.
No issues so far with this configuration, although we have observed transaction-log latencies of up to 20 minutes between the primary and secondary replicas.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]