Break Free of Legacy Databases
Since the last two decades, enterprises have been paying massive dollar amounts to keep buying expensive licenses of legacy DBMS Systems like Oracle, DB2, SQL Server, Sybase ASE etc. An overwhelming majority of enterprise data architects hate paying such exorbitant amount of money for these legacy databases. These frustrated and helpless souls have a dream that one fine day they will be able to break free of these legacy databases. As database developers ourselves, the team at Replicant witnessed this recurring theme across all enterprises globally. Every data architect and DBA wants to reduce their Oracle, SQL Server and DB2 bills. Who will rescue these helpless souls?
Yes, your friend Replicant is here to solve your problem. The next few paragraphs will explain how to reduce your legacy database bills by a HUGE amount.
Any operational database system serves two primary purposes: (a) It serves as the System of Record which means applications that generate data write all the data into this database via PL/SQL stored procedures (the INSERT, UPDATE, DELETE stuff) (b) It serves as the System of Access which means applications that generate operational reports perform operational (transactional) queries on this system. Traditionally, a single expensive (or a set of expensive) legacy database(s) have served the purpose of SYSTEM OF RECORD and SYSTEM OF ACCESS.
Replicant provides you the magic that empowers you to use different databases for SYSTEM OF RECORD and SYSTEM OF ACCESS. Replicant enables real-time continuous transactional replication across heterogeneous databases guaranteeing transactional consistency; this magic sauce allows enterprises to retain trusted OLTP systems like Oracle, DB2 for their SYSTEM OF RECORD, but choose inexpensive databases like Postgres, MySQL etc. as the SYSTEM OF ACCESS. This separation of workloads across different systems has two major advantages
Reducing the workload on the legacy system like Oracle enables you to significantly cut your resource capacity and hence, the license bill. For example, if the workload has an even mix of writes and reads, the legacy database installation requires only 50% of the previous capacity and hence, the database bill reduces by half.
Splitting the reads from the writes would also allow for the reads to be faster. Doing both the reads and writes in a single system would lead to additional contention and locking, but splitting it across systems means less contention and less locking.
Let us look at some real numbers now. Imagine you are using a Oracle Exadata Full Rack today for your operational system, costing you a huge $1.7M for the appliance and Oracle support. (Refer cost of “Exadata Database Machine X7-8 High Capacity (HC) Full Rack” in http://www.oracle.com/us/corporate/pricing/exadata-pricelist-070598.pdf).
Using Replicant and Postgres/MySQL as the SYSTEM OF ACCESS, you can downgrade to Exadata Half Rack and still achieve the same read and write performance as before. This will reduce your Oracle bill by half (Exadata Half Rack plus support costs $750K) and bring down total cost of system to less than $1M.
So what are you waiting for? Contact us at sales@replicant.tech and save millions of dollars every year.