Clienteling isn’t a new theory. It can be traced back hundreds of years when shopkeepers …
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.
The new release of SymmetricDS 3.9 will help you:
The Dashboard was improved with additional views and a new layout that can be customized by the user. Overall performance is more visible from a health view that scores the replication status and a speed view that measures the rate of incoming and outgoing data replication. A recent activity view shows the local node’s processing with row performance, while batch views show activity at the node and batch level. A node view shows a summary by node of replication status, sorting by any backlogs.
The Dashboard and Batch screens update immediately with row statistics as batches progress, using progress bars and row counts. Using remote node status over WebSockets, the web console gives better visibility of data replication progress so the user can see what is currently happening. Remote node status only activates when the user enters a screen, but it can also be disabled, falling back to the older method of waiting for statistics on acknowledgement of the batch.
Custom jobs can be configured to run user-provided scripts on a schedule at specific nodes. By providing a SQL script, the user can automate tasks and perform database maintenance across one or more nodes. Advanced scripts can be written in BeanShell or Java, which can access the services API of the replication engine for the node.
A “load only” node can directly load a database without storing any runtime tables or other objects in that database. During setup of a new node, the user can select “Other” for the database type to create a “load only” node for their database. If the JDBC driver is not already included, the user can upload the driver. Configuration and runtime information for the node are stored separately in an internal database. Using a “load only” node expands support to any database that supports JDBC.
Staging was enhanced with compression to conserve disk space and encryption to protect data. Staging data to disk improves performance by reducing the time resource are held open in the database and over the network. The enhanced staging includes parameters that control staging with encryption strength and compression level.