A high-performance backend cache system. It is intended for use in speeding up dynamic web applications by alleviating database load. Well implemented, it can drops the database load to almost nothing, yielding faster page load times for users, better resource utilization. It is simple yet powerful.
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.\
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Phpfastcache?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing code/behavior)
[ ] Deprecated third party dependency update
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation/Typo/Resource update that does not involve any code modification
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Co-authored-by: Geolim4 Geolim4@users.noreply.github.com
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.\ If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Phpfastcache? Put an
x
in the boxes that applyAgreement
I have read the CONTRIBUTING and CODING GUIDELINE docs
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...