Any logical replication solution can become complicated when you have a large system with multiple databases that have to have HA and DR on the architecture. The more components you have, the more SharePlex services you need. That can become complicated to manage only because of the way logical replication works. It's not necessarily a SharePlex issue. It's a logical application issue.

Scalability wasn't really something that we tested for, since we have been using it mostly with one-to-one relations, i.e., one target for one source.

It is quite scalable. Support has given us different ways to scale while managing and maintaining databases that are in the terabytes. We haven't had any situations where the scalability of replication became a major issue.

SharePlex is being used extensively in our organization. It's a part of our "DNA," primarily when it comes to high availability of applications and maintenance, because without having real-time data available in the other data center, we wouldn't be able to provide this kind of availability and scalability for our infrastructure and for our customers. 

We are increasing usage. As we are getting more and more customers, we are expanding and are getting more IoT data. As a result, we are doing more and more implementations of SharePlex. It is literally in all our geographies. We have it in our China data centers, we have it in Canada, in the U.S., and Europe. We have it implemented across the world.

The solution is very scalable. It can handle a terabyte of data easily.

Only in version 5. Scalability has improved, even in minor versions, from version 6 and up.