After the cake migration project we’ll work on something we had pending for a long time which is to have a proper scheduler. eramba runs a “cron” every hour, day and year which churn data and update charts, statuses, send emails, etc.
We’ll move all of that to a scheduler with a FIFO style of queue which will be processed every minute (instead of three crontab entries there will be one). As we do this, we will also “decouple” eramba so you choose on System / Settings for each module (internal controls, risks, compliance, dashboards, scheduler, etc) which:
- write database to use
- read database to use
This will allow eramba to read from multiple +R slave databases and writing in (for a start) on only one. Things like dashboard calculation, status calculation, pdf processing, etc are a b…ch and take a ton of DB I/O and therefore we are pretty confident this will let you scale your deployment pretty easily.
There is no GIT for this yet as we first need to complete the endless and super expensive cake migration, but chances are that just after we finish this project we’ll start with decoupling and the first one to decouple as stated before will be the crontabs into a “Scheduler” module.