Can Redis Be Used In MTA Mapping Callouts For Throttling?
(Doc ID 2635325.1)
Last updated on FEBRUARY 04, 2020
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Qn1:On : Oracle Communications Messaging Server 22.214.171.124.20190704 64bit (built Jul 4 2019) version, MTA
Can redis be used in MTA mapping callouts for throttling?
Mapping callouts for connection throttling can be made to MeterMaid and memcached. We are seeking to find out whether work is ongoing to add support for mapping callouts to redis that will allow its use for throttling?
The messaging server is getting more and more support for using redis for various functionality - MTA databases, sieve extension, smartsend plugin, and autoresponse tracking. Allowing redis for mapping callouts seems to be an obvious additional use for which it could be suitable, and would provide a degree of persistence (and possible HA) that is otherwise lacking, especially since the underlying support for redis already appears to be present in the messaging libraries.
Currently it looks like it is necessary to deploy redis (if its use for any of the above functionality is desired) *and* either MeterMaid or memcached. Having to deploy multiple technologies is additional administration and inconvenience, which is why being able to use redis for all these functions would be very much preferable.
If there are good reasons why redis is *not* suitable for use with mappings callouts then that would also be helpful for us to understand.
Qn2:Does MTA supports TLS connections to a Redis service? If so, how is that configured?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document