There is only one database node in the cluster. The node hides behind the GW. All ordinary clients are not allowed to directly access the database node except the administrator by some specific or...

The two nodes of the cluster hide behind the GW. All of the ordinary clients are not allowed to directly access either of the database nodes except the administrator by some specific or provisional...

  All clients connect to the VIP on the DBTwin Main Gateway(abbr as GW). The GW does the function of automatic(without any source code modification) read-write splitting and load balance. Through ...

If appropriate, the result set of proper select requests will be cached in the  GW. If the GW detects that the same select request, together with its   parameters has been reissued, the GW will ret...

  Crash of any node(either DB-A or DB-B) will not affect the other one and clients will continue to access database services without long downtime(less than 20s) of business service.     DBTwin Ac...

DB-A will be chosen as the Primary Node responsible for real time and multi-theaded data synchronization to DB-B. There are always two real-time consistent and alive datasets which enhances the re...