Why is Always On NOT an AA database cluster but DBTwin is ?

In essence, Always On is just a log-based real time backup tool. It is NOT an AA database cluster. However DBTwin is a totally true AA database cluster. Because:

1. Data synchronization

    Always On: log-based, single threaded, syncing all DMLs and DDLs within a database.

    DBTwin: not log-based, multi-threaded, syncing data and a few necessary DDLs.

    Synchronization Comparison between DBTwin and Always On

    https://lnkd.in/gvCu4Wb4

2. RTO, RPO

    Always On: zero data loss in synchronou mode NOT guaranteed.

    DBTwin: zero data loss guaranteed, near zero downtime.   

    Why Always On doesn't have Guaranteed Zero Data Loss(GZDL)?

    https://lnkd.in/giaTX-vT

3. Read/write separation and loadbalance

    Always On: source code rewrite to manually separate reads from writes.

    DBTwin: automatic read/write separation and loadbalance without source code rewrite.

    Why is Always On NOT A TRUE loadbalancer?

    https://lnkd.in/gpERGjmW

4. Misc features:

    Always On: none.

    DBTwin: other usefull features.

    How can you avoid the accidental deletion of a table or even a database?

    https://lnkd.in/gN6D_kKP

5. Maintenance:

    Always On: complicated, need for dedicated DBAs.

    DBTwin: simple, no need for dedicated DBAs.

For details, please visit:

https://www.zhetides.com