Why Must ISC Use Cassandra For The Conversion Cache?
(Doc ID 2779292.1)
Last updated on MAY 25, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Why must ISC use Cassandra for the conversion cache?
There are questions about the design of having ISC use a table in Cassandra for its conversion cache. Why not use local files like with classic store?
It is understood that the conversion cache is intended to prevent ISC from having to convert the same attachment multiple times, but...
How likely is it that the same attachment will be resent to users on the same Cassandra cluster/keyspace via different access tier systems within the lifetime of the cache entry?
How bad would it be if the ISC processes on different access tier systems performed the same conversion?
It seems like using local disk storage on the access tier system would be simpler, faster, and less load on Cassandra.
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