Is there any better solution besides Always On on the market?

Is there any better solution besides Always On on the market?

Reasons:

a. High reliability: Even the sync mode in Always On has NO

                     guaranteed zero data loss when in disaster,

                     let alone the async mode. It means that the

                     switching process is risky and people rarely

                     use the automatic switching mode(sync mode) due to

                     its obvious performance impact.

                     Why Always On doesn't have Guaranteed Zero

                     Data Loss(GZDL)?

                     http://www.zhetides.com/nd.jsp?id=24

b. High availability: Since the disaster switching process is risky,

                     it means the length of downtime is variable

                     and depends on the skill of the attendant which

                      means there is NOT guaranteed max downtime.

c. High performance: The sync mode has obvious impact on performance.

                     What's more, Always On has NO automatic r&w splitting

                      and loadbalance which is crucial for the separation of

                     OLTP/OLAP and hence the db performance.

                     Why is Always On NOT A TRUE loadbalancer?

                     http://www.zhetides.com/nd.jsp?id=23  

d. Installation and maintainence: Maintainability is crucial

                     when a disaster strikes. The more complex the

                     maintainence, the more unpredictable and longer the

                     length of downtime is. Always On needs a least one

                     professional skillful DBA to take care of.

THEN WHICH IS MUCH BETTER?

The answer is: DBTwin Active-active Database Cluster.

1. DBTwin Features:

a. High reliability: When a disaster strikes, one node is down, another

                              node continues with Guaranteed Zero Data Loss(GZDL) automatically.

b. High availability: near-zero downtime. When a disaster strikes, one

                              node is down, another node continues running automatically. The

                              service downtime is less than 20 seconds.

c. High performance: automatic r&w splitting and load balance without any

                               source code change. This feature is UNIQUE on the

                               market. It is crucial for the separation of OLTP/OLAP

                               and so the db performance.

d. Simple installation and maintainence: Why do many people prefer

                     buying third-party solutions over SQL Server

                     self solutions? Maintainability is an important factor.

                     An ordinary engineer can be qualified for the job.

2. DBTwin Benefits:

a. Free from the fear and accountability of data loss.

b. Free from the shock and accountability of service disruption.

c. Free from the drowsiness and fatigue of 3AM.

A GOOD TOOL IS FAR BETTER THAN A TOP-LEVEL DBA.

A foolproof and one-stop solution.

More info: https://www.zhetides.com