Issue & Reproduction Steps

As a developer, I want to ensure that the caching solution is scalable, So that it can handle high traffic without becoming a bottleneck or consuming excessive server resources.

Once caches (Settings and Screens) are implemented, multiple concurrent users will access to multiple different resources and must experience a fast response to the cached resources.

Solution

• improve the metrics cache
• create settings factory
• use factories to start the cache metrics

How to Test

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-20917

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.