Powerful solutions/services for your Database updates.

The Philosophy

You're a bank. You just updated your mortgage Database with a product rate change. What else do you want updated with that new rate?
Well, we have 4 other legacy databases (say 2 Oracle, 1 DB2, 1 NoSQL) that need to be updated with that rate. Fine. We need 6 important HTML pages updated as customers need to see the new rate. Fine. We need 2 PDF files updated. Fine. All based on a single update DB record? Correct. Does DBUpdate need access to our databases? No.

DBUpdate.net allows you to take advantage of making any kind-of Database change to automate tasks which rely on that data. You can update other disparate Databases with that change, you can update critical HTML webpages, you can update PDF documents, you can update Open Banking information. In fact, you can turn that single Database change into any format you require.
DBUpdate.net uses tried and true technologies (SQL, XML, XSL, XSLT) to automate the necessary and envisioned down-stream processes of a single DB change. Read our white-paper on the underlying services.
The four main benefits of DBupdate are:
- It provides a low-cost centralised-managed synchronisation process for your heterogeneous DB environment.
- It removes human coordination issues between updates of DBs and the separate maintenance of critical HTML/PDF files.
- It does away with the need for external or vendor synchronisation programs/processes to connect to internal DBs thus eliminating firewall/security issues.
- Change your DB structures or HTML/PDF files? Just update the associated XSL files all within DBUpdate.
An enterprise solution of DBUpdate coupled with an event-driven messaging system such as Kafka is a powerful combination. See the demo .
Note: DBUpdate can now interact with Open Banking as an industry-wide Source-of-Truth. See how we do it .

Use Cases

DB Synch

Webpage Updates

PDF Updates

External Data

DB Synch

Webpage Updates

PDF Updates

External Data

Our Message to Everyone

Use case: DB Synchronisation

In a single sentence: synchronising legacy/disparate DBs is hard.

Any solution to provide atomic updates across legacy DBs is very expensive, complicated, and fraught with constantly-changing security/networking/firewall issues. For example, 2-phase commit (2PC) has been used for the past 30+ years, and still no one is quite happy with it. 2PC issues include latency, blocking, scalability, throughput, transaction clogging, and availability issues. Some solutions require a multitude of DBMS drivers, and/or userid/passwords to create connections into the legacy DBs from outside of their domain thus creating security issues.
DBUpdate does away with all this. You can be 15 firewalls deep in your network, and if you can access the outside world you can use DBUpdate.
DBUpdate takes a Database update and creates a script based on your rules. Each legacy DB has it's own rules/syntax and thus will produce a script for that particular DB and DBMS. The beauty is that each type of DB change can have it's own Source-of-Truth (SoT or System-of-Record) DB. In fact, DBUpdate can be used to create a verification script to ensure that the data within the legacy DBs matches the SoT DB.

Use case: Webpage Updates

Obviously, the importance of HTML webpages being correct and up-to-date is critical in today's web-based world.

Companies need the HTML webpages to be updated as soon as DB changes are made. 2 ways to do this: 1 - is to dynamically generate the HTML on each user visit. While this resolves any data-integrity issues, it certainly is non-optimal since DBMS accesses are expensive and DB changes may be only sporatic, DB servers may be down, and the web-server needs access to the data thus with potential networking security issues, or 2 - update the HTML upon a DB change to create a new static HTML file. This is the tack DBUpdate takes.
DBUpdate can use rules to update a HTML webpage file based on the DB update data packet. The service will return the HTML which has only updated the particular data element leaving all other elements/formatting untouched. The calling process can then take this updated HTML and overwrite the production HTML file.
No human intervention required; no non-optimal processes required. Your customer-facing documents can be automated.

Use case: PDF Updates

PDF files are the main way organisations disseminate their product/service information and Product Disclosure Statements (PDSs). As with HTML webpages, it is vitally important they are correct and up-to-date.

Your rules will contain the location, font, size, etc of the element that is to change. As with HTML files, DBUpdate will return the newly updated PDF to the calling process to overwrite the production PDF file.
No human intervention required; no non-optimal processes required.

Use case: External Data

There is no reason that any well-formed, structured, verified, internal/external data packet can not be used to update other DBs, HTML webpages, PDF documents, or data interchange.

Examples could be adding government data into a webpage or PDF. Or adding competitors information to webpages to showcase your products/services. Or Open-Banking data.
Another example is data interchange between your organisation and external parties. Both parties could create a common set of rules and entered into DBUpdate acting as a transformation hub.

We REALLY Need to Help Our Planet

Please contact us if you have any questions or suggestions as to how we can crush this in more effective and interesting ways.
Privacy: The data that you enter into this system will be personal to you. We respect that and will only share the data with the people you so choose. We understand how important this is to you.

"You are braver than you believe, stronger than you seem, and smarter than you think." - Christopher Robin to Winnie-the-Pooh.

XSL transformations beautifully done by Saxon-JS.

©2021 www.dbupdate.net