New on the HB dev blog:
By leveraging a SQL database for caching, Solid Cache enables Rails applications to store a greater volume of data for extended periods, overcoming the limitations imposed by the cost and capacity of memory storage.
Read the article: https://www.honeybadger.io/blog/solid-cache/?utm_source=mastodon&utm_medium=social
I deployed #solidcache into production today. In the past I've asked around about what kind of performance people had been seeing and gotten back nothing, so, a quick thread about my experience, and a subtle gotcha to avoid if pre-warming/transferring.
@jaredmoody I’m actually using #SolidCache in production for a rails app providing a RestAPI that serves measurement data. It’s not as fast as caching with redis, but its way faster than always rendering the same responses. AND because of doing it with a database (postgres) it’s more affordable caching larger amounts of data.
Any #ruby / #rails / #rubyonrails friends out there have experience running #SolidCache in production?
The pitch I heard was "NVMe drives are fast enough now to store the cache in the database" - but I haven't seen discussion of that database being over a network (which is AFAIK how most people do this) vs directly attached, or real production stories.
