[MXS-3664] Built-in caching in nosqlprotocol Created: 2021-07-09  Updated: 2023-07-28  Resolved: 2023-07-28

Status: Closed
Project: MariaDB MaxScale
Component/s: nosqlprotocol
Affects Version/s: 6
Fix Version/s: 23.08.0

Type: New Feature Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-4573 Benchmark nosqlprotocol Closed
Epic Link: MongoDB Protocol Support
Sprint: MXS-SPRINT-183, MXS-SPRINT-184, MXS-SPRINT-185, MXS-SPRINT-186, MXS-SPRINT-187

 Description   

As nosqlprotocol is the first module in the routing chain, the regular cache filter will be of value. However, not as much as one would expect, as, since the cache stores result sets, nosqlprotocol would at every cache hit still have to perform the JSON->BSON conversion, which is a heavy operation.

If instead the nosqlprotocol would have its own cache that stores BSON data, then a cache hit would require no processing but the data could simply be sent to the client.


Generated at Thu Feb 08 04:23:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.