You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we are deploying in production, our Redis events will not be used. To be more efficient, we should add a feature to turn Topic off completely via a build flag. This would add a noop function for all Topic API calls, to ensure that no other code needs to be changed.
Advantages:
V8 can better optimize the server code by detecting dead code and routing around it.
No need to have a complex Redis-Node interaction in the Event Loop if it is not used.
Database does not record events when they are not used.
@IMA-WorldHealth/bhima-core What do you think?
The text was updated successfully, but these errors were encountered:
This commit adds environmental variable control of the events emitted by
Topic. By setting the variable `DISABLE_EVENTS` to false, no Redis
subscriptions will be made at runtime. In fact, the code is read as
dead code and returns immediately on entry into the function.
ClosesIMA-WorldHealth#948.
This commit adds environmental variable control of the events emitted by
Topic. By setting the variable `DISABLE_EVENTS` to false, no Redis
subscriptions will be made at runtime. In fact, the code is read as
dead code and returns immediately on entry into the function.
Closes#948.
As we are deploying in production, our Redis events will not be used. To be more efficient, we should add a feature to turn Topic off completely via a build flag. This would add a
noop
function for all Topic API calls, to ensure that no other code needs to be changed.Advantages:
@IMA-WorldHealth/bhima-core What do you think?
The text was updated successfully, but these errors were encountered: