Microsoft had release their JDBC drivers to support AlwaysOn AG since SQL 2012 R2 but I am not sure whether DRCUM release updated their driver. In any case, anyone have experience to configure CAS, ADS and CSS connecting to a SQL Server 2016 no domain alwayon AG ?
I've recently asked this question of product management, the response was that no the drivers used by CAS/ADS/CSS/RUMC do NOT support SQL Always On, because the drivers to do so are significantly slower than the drivers we use, and would result in a performance bottleneck at even moderate loads.
The products use a third-party JDBC driver - jTDS
Sorry that link was an internal one. The content just backed up what I said previously. Stating in some cases the Microsoft JDBC driver can be up to 60% slower than the jTDS one for CAS workloads.
I believe the JDBC driver is using Microsoft provided as CAS, ADS, CSS and even RUM can only run on windows, but in any case since it based on third-party JDBC driver -jTDS which shouldn't be said that the performance very much depend on jTDS. I read that jTDS do support AlwaysOn but all the nodes in the SQL Server AlwaysOn AG has to be within the same subnet.
Another issue is the SID of the db account used for all the SQL Nodes has to be the same as during the failover CAS, ADS, CSS and RUM will use the same user and credential to access. But that's provided we're using SQL user but would resolve if we use Windows AD users.