Hi there,
Always On is the "Buzz Word"
the HA technology behind it are two things ... Always On Failover Cluster and Always On Availability Groups
So you are talking about AOAGs
AOAG -> It is not a replication; I would prefer to call it "Mirroring on steroids."
So, it mirrors your complete data from node A to B.
In a normal/general setup, it only has one connection string, and you do not need to change your application. But to get the full advantages of an AOAG, the application should be able to differ between Read and Write Intents. So will be able to route your Read-Workload to a secondary node, all Write-workload will be routed to the primary node.
https://www.sqlshack.com/how-to-configure-read-only-routing-for-an-availability-group-in-sql-server-2016/
Failovers - Both are possible!
Automatically - depending on node count - in case of a failure, the role of the primary server will failover automatically to another (secondary) node.
In case of maintenance... you can do this manually (SSMS, Batch, Powershell...)