Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the Significance of solid_cache over traditional one? #220

Closed
Anush-Kumar-S opened this issue Sep 10, 2024 · 1 comment
Closed

Comments

@Anush-Kumar-S
Copy link

Team, traditional cache uses the memory. But solid cache is going to use database.

If database is used, then additional queries will be required to get and store the data.
And also why we should have new database for this. Won't it increase the maintenance cost? Why can't we use thew same application's database

@dhh
Copy link
Member

dhh commented Sep 10, 2024

From the opening paragraph of the README: "Solid Cache is a database-backed Active Support cache store that let's you keep a much larger cache than is typically possible with traditional memory-only Redis or Memcached stores. This is thanks to the speed of modern SSD drives, which make the access-time penalty of using disk vs RAM insignificant for most caching purposes. Simply put, you're now usually better off keeping a huge cache on disk rather than a small cache in memory."

@dhh dhh closed this as completed Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants