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 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 uses tried and true technologies (SQL, JSON, XML, XSL, XSLT) to automate the necessary and envisioned down-stream processes of a single DB change. Usage can be either via the console or API.
Of course, it doesn't have to be DB changes. It could be any well-formed data packet from any source which can be transformed into another useful format for a different application or data interchange. DBUpdate doesn't care.