Backend improvements

Wow! Has been a while since our last changelog!
We have been busy getting a refactored UI ready, developing AI nodes, and finalising a large DB migration.
We're now on track to getting most of these things released shortly and with faster development as a result.
Here's a quick summary of some recent changes we have deployed:
Updates to reporting caching
We have rolled out a new caching system for reporting to remedy some issues users were seeing with IDs appearing instead of names, and some large asset lists not loading.
The caching used is now a lot more performant and should have minimal issues. We still plan to move our assets DB in the future to remove the need for complex caching layers entirely.
New conversion deduplication process
Just now we have rolled out a new conversion deduplication process that was needed after our DB migration, as it became possible for multiple conversions to happen in rapid succession.
Our new logic has a 5 minute and 3 hour deduplication window that works like this:
Conversions with the same hit/tx received in a 5 min window will be deduplicated, even if the revenue value is different -- preventing rapid updates of an existing conversion
If a duplicate conversion arrives after 5 min but before 3 hours, if the revenue has not changed, we will drop it. If the revenue has changed, we will consider it an update and process as such
After the 3 hour window, we will reprocess/update any existing conversions, regardless of revenue
Improved Optimizer queries
We have also made optimisations to the way queries from The Optimizer work, dramatically reducing the load impact this was happening on our system.
These were becoming problematic and impacting reporting speed for all users + delaying ingest at times.
Added force postbacks option
You can now pass force_postbacks=true
 into postbacks to force firing of events to traffic sources even if they have happened before, i.e. are updates.
This combined with our new conversion deduplication means we can soon roll out conditional postback options on the Update Conversions page, i.e. the ability to choose to:
Not fire any postbacks to traffic sources
Fire for every hit uploaded
Only fire for those that are new conversions