SQL Server 2016 Primary and Backup We have a new production box with two SQL servers,SQL Server 2016 Standard edition.
The current plan is to have:


One primary SQL server
Backup SQL server:only SQL Report server,which points to primary server.


Can you please suggest any good replication strategy to move data from primary to back up server and which does not use Single User mode.
Realtime replication is expected.

In primary server lots of insert/update happens and will be online 24/7.
New into Replication.

Only one database in Primary SQL server,have to replicate the same db tables/views/triggers etc  into Backup server.

Have done some research on replication(Snapshot,Transaction,Merge),but i am not sure about the Single User mode thing in this context.
AlwaysOn Active Secondaries should provide the capabilities you're looking for, including virtually realtime replication of data, and reporting capability on the secondary.


  The Always On availability groups active secondary capabilities include support for read-only access to one or more secondary replicas (readable secondary replicas). A readable secondary replica can be in either synchronous-commit availability mode, or asynchronous-commit availability mode. A readable secondary replica allows read-only access to all its secondary databases. However, readable secondary databases are not set to read-only. They are dynamic. A given secondary database changes as changes on the corresponding primary database are applied to the secondary database. For a typical secondary replica, the data, including durable memory optimized tables, in the secondary databases is in near real time. Furthermore, full-text indexes are synchronized with the secondary databases. In many circumstances, data latency between a primary database and the corresponding secondary database is only a few seconds. 


This technology also provides the ability to failover to the secondary in the event of a hardware or software failure on the primary, with minimal or no data loss.

Transactional replication won't prevent access to the data at the subscriber.  Transactional Replication offers a huge amount of customization and requires quite a lot of configuration and management, whereas AlwaysOn provides a simplified way of making an entire database or set of databases highly available.