<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Andrew Morgan on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/amorgan/</link><description>Articles written by Andrew Morgan on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 May 2026 15:23:30 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/amorgan/index.xml" rel="self" type="application/rss+xml"/><item><title>When Should You Use a Cache With MongoDB?</title><link>https://foojayio.github.io/website/today/when-should-you-use-a-cache-with-mongodb/</link><pubDate>Tue, 05 May 2026 15:23:30 +0000</pubDate><guid>https://foojayio.github.io/website/today/when-should-you-use-a-cache-with-mongodb/</guid><description>&lt;p&gt;From time to time, I&amp;rsquo;ll run a &lt;a href="https://www.mongodb.com/events/mongodb-schema-design-reviews/?utm_campaign=devrel&amp;amp;utm_source=third-party-content&amp;amp;utm_medium=cta&amp;amp;utm_content=cache-foojay&amp;amp;utm_term=tony.kim" target="_blank" rel="noopener noreferrer"&gt;design review&lt;/a&gt;
 for an application being migrated from a relational database onto MongoDB, where the customer shares an architectural diagram showing a caching layer (typically Redis) sitting between the app server and MongoDB.&lt;/p&gt;
&lt;p&gt;I like to keep the architecture as simple as possible&amp;mdash;after all, each layer brings its own complexity and management costs&amp;mdash;so I&amp;rsquo;ll ask why the caching layer is there. Of course, the answer is always that it&amp;rsquo;s there to speed up data access. This reveals a misunderstanding of both the reason why caching layers were created and what MongoDB provides.&lt;/p&gt;</description></item></channel></rss>