Question 1

How to set up Cache Crispies with Redis for caching?

Accepted Answer

Configure the cache store in CacheCrispies.configure to use a Redis store like DalliStore, and ensure models have updated_at columns. The README provides an example with ActiveSupport::Cache::DalliStore for custom cache stores.

Question 2

Cache Crispies vs ActiveModelSerializers: which is better for performance?

Accepted Answer

Cache Crispies is optimized for speed with built-in caching, often outperforming ActiveModelSerializers in benchmarks, especially when caching is enabled. However, ActiveModelSerializers might be more familiar for teams already using it without caching needs.

Question 3

How to handle nested associations in Cache Crispies?

Accepted Answer

Use the 'with' option in serialize or merge statements to nest serializers, and leverage nest_in blocks for hierarchical JSON structures, as shown in the complex serializer example with ingredients.

Question 4

Best practices for cache key generation in Cache Crispies?

Accepted Answer

Include runtime options in cache_key_addons to prevent stale data, and use dependency_key for logic changes. The README explains that cache keys combine serializer content, model cache_key, and addons.

Question 5

Does Cache Crispies support Rails 7 or later?

Accepted Answer

The README lists support for Rails 5 or 6, with others potentially working but untested. For Rails 7, check the GitHub repo for updates or run tests locally with Appraisal to verify compatibility.

Question 6

How to bust cache in Cache Crispies when data changes outside models?

Accepted Answer

Use dependency_key to manually invalidate caches for serializer logic changes, and ensure cache_key_addons account for external factors. Editing serializer files also busts caches automatically.

cache_crispies

What is cache_crispies?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions