BOPIS, BORIS, and Curbside Pickup offer consumers and retailers the best of both worlds. …
Cloud-native POS platform for seamless omnichannel customer experience.
A single hub for all promotions campaigns.
The most advanced synchronization solution for databases and file systems.
Data configuration and batch automation across different disparate systems and vendors.
BOPIS, BORIS, and Curbside Pickup offer consumers and retailers the best of both worlds. …
Automated Personalization is revolutionizing retail—Discover how a small investment can bring a big impact. Online …
What is the Composable Store? Composable is one of the most common terms being thrown …
Creating a replication of hundreds or even thousands of similar databases and also being able …
One of the many advantages of using SymmetricDS is that you’re able to leverage the …
Overview The cloud is here to stay and getting data there to utilize all it …
Mark Michalek, a highly accomplished professional in the retail technology space, has been promoted to …
After nearly a century in business, the legendary Canadian fashion retailer is retooling to streamline …
Columbus, OH, June 6, 2023 – The Paper Store, a leading specialty retailer offering a wide …
Cloud-native POS platform for seamless omnichannel customer experience.
A single hub for all promotions campaigns.
The most advanced synchronization solution for databases and file systems.
Data configuration and batch automation across different disparate systems and vendors.
Common batch mode was enhanced in SymmetricDS 3.11 to allow any group of nodes to share batches. Let’s look at what common batches are and why this is a big deal for database replication with more than a couple nodes.
In the early history of SymmetricDS, it didn’t include the concept of common mode for batches. The router service would put changes into separate batches for each node that needed them. For example, if there were 4 nodes on the system, and the router service found 3 changed rows of data, it would write a new batch for each node and place the changes inside. The screenshot below shows an example, with batches 58 through 61.
Starting in version 3.0, it was optimized to route the change once into a common batch for all the nodes. There is still a separate batch entry to track the status for each node, but they share the same batch number and the same batch data. The screenshot below shows batch 63 is shared.
Why is sharing batches better? Because common batches are more efficient to route, extract, and purge. We can see the difference when looking at the runtime model. Changes are captured as “Data” and assigned to one or more “Batches”. The many-to-many relationship between the two is associated in “Data Events”. With common batches, the router service has less work to create batches and the purge service has less work to clean up later. The illustration below shows the difference when routing 3 changes to 4 nodes.
Common mode has been around, but it was limited to channels with only “default” routers and uni-directional replication. In other words, it worked for a channel when sending one-way to all nodes, but not for any arbitrary group of nodes. With the new SymmetricDS 3.11 release, any group of nodes are eligible for a common batch. In other words, now common batch mode is always enabled! Routing to groups of nodes to subset data by chain, region, district, and any other combination now benefit from common mode sharing of batches.