|
 The Enyo Mirror product
was originally developed to be an underlying technology supporting the Enyo Commerce platform.
Its purpose is to mirror data from the ERP system to a separate environment and in some cases
back to the ERP system.
This functionality is however very generic, and can be used in a number of other scenarios
where you would like to mirror or replicate a large segment of data from one location to one
or more destinations.
Applications
Apart from obviously using it for Enyo Commerce, we have also used it in a couple of other
situations:
- Take strain of the central ERP database, e.g. for heavy BI / data warehouse operations
- Expose only the data needed for a specific purpose. (security)
- Generate general copies for snapshots of the current data
- Ability to mirror data between different database vendor’s engines
(e.g. Oracle <-> SqlServer <-> DB2 etc...)
- Ability to mirror core data between ERP systems, even running different databases.
(E.g. from Microsoft XAL <-> Dynamics Ax/NAV <-> etc…)
What’s the difference to Database built-in Replication?
If the situation allows it, we definitely recommend you use the built-in replication features
of the database in question. Because they usually have built-in optimizations, that really
doesn’t cost anything in terms of performance.
However if for some reason your system does not allow changes to the database, (e.g. such
as the GUID columns / Custom triggers etc. added to each table for SqlServer), OR you would
like to mirror data between 2 different database engines (e.g. Oracle and SqlServer), Enyo
Mirror offers a complete solution.
How it works
Enyo Mirror does only observe the source database, and does therefore only perform read operations,
which allows it to have a minimal impact on the daily performance. Since ERP system databases
are often working overtime already this is a major issue to many companies.
The application itself can run in a few different modes; one optimized for mirroring data
over the internet with a limited bandwidth, and a mode optimized for local network access,
depending on the usage and needs for the application.
Performance
Depending on configuration and hardware and bandwidth, Enyo Mirror has an excellent performance.
One of our previous installations held 8 GB of data online with a latency of less than 5 minutes
over a regular 10Mbit connection. The source database was an Oracle 10 running on UNIX and
Enyo Mirror was running on a regular Srv2003 with 4 CPU cores and just 4 GB of memory.
From our experience the limit is not the amount of data that is to be monitored but the amount
of changes within the data and connection the changes are supposed to be transferred over.
|