Caching does not implement a max size

[matthewelwell]

Currently the caching implementation does not implement a max size. We should add a configurable limit to the size of the cache to ensure that there are no memory concerns when using the cache implementation in the client.

[matthewelwell]

@JFCote @vpetrusevici - mentioning you both here as I know you both worked on the caching implementation. I'm keen to get your thoughts here on whether there's a reason that a max size was not implemented originally.

[JFCote]

@matthewelwell As far as I remember, I think I didn't add this kind of limitation as it was a "first draft" and "best effort" kind of thing.

I definitely think it would be a great improvement to prevent very big users to bust the memory of their applications.

[matthewelwell]

Understood - thanks @JFCote.

[flagsmith]

Flagsmith feature linked: secret_button
Default Values:

Environment	Enabled	Value	Last Updated (UTC)
Development	✅ Enabled	{colour: "#080808"}	2024-04-30 22:54:05
Production	✅ Enabled	{colour: "#080808"}	2024-03-28 20:58:49

[flagsmith]

Flagsmith Feature secret_button has been updated:

Environment	Enabled	Value	Last Updated (UTC)
Development	❌ Disabled	{colour: "#080808"}	2024-06-04 16:36:40

[flagsmith]

Flagsmith Feature secret_button has been updated:

Environment	Enabled	Value	Last Updated (UTC)
Development	✅ Enabled	{colour: "#080808"}	2024-06-04 16:40:28

[flagsmith]

Flagsmith Feature secret_button has been updated:

Environment	Enabled	Value	Last Updated (UTC)
Development	❌ Disabled	{colour: "#080808"}	2024-06-04 16:41:46