Managing the changes to the database backend of WordPress is a much different design than integrating GitHub into our development model. When a database changes, there are certain things that can be automated using database tools like triggers and stored procedures. But we can’t build a simple audit trail on the database side because it is too risky.

Fortunately, our Founder has been writing DataMart and DataWarehouse systems for most of the last 25 years. The main point of writing DataMart and DataWarehouse systems is to monitor changes to transactional databases over time and store the status of a normal database once a day, or once an hour is an amazing tool for many companies who store all of their data in a handful of databases.

Being able to do some of these things outside of WordPress plugins allows some flexibility. We love our ability to do unique designs for different clients.

I just see a lot of value in being able to combine a relational database with more advanced schemas like Datamarts and DataWarehosues. The bottom line that someday, I envision building Datamarts that are based of a transactional system like the WordPress Database Schema.

I just want a better audit log, a better, more detailed database that will allow me to identity the way that systems grow and change over time. I spent a heck of a lot of time building Datamarts and DataWarehosues and in theory it shouldn’t take that much time to do. Pulling data out of a transactional system, and storing the results OVER TIME. That is the main purpose of DataMarts, and I feel that design is extremely applicable here. It shouldn’t take long.