Alex & Chris get into a fairly recent technological change at CodePen where we ditched <a href="https://blog.codepen.io/2019/09/18/237-elasticsearch/">our Elasticsearch implementation</a> for just using our own <a href="https://www.postgresql.org/">Postgres</a> database for search. Sometimes choices like this are more about team expertise, dev environment practicalities, and complexity tradeoffs. We found this change to be much better for us, which matters! For the most part search is better and faster. Postgres is not nearly as fancy and capable as Elasticsearch, but we werent taking advantage of what Elasticsearch had to offer anyway.



For the power users out there: it&#8217;s true that we&#8217;ve lost the ability to do in-code search for now. But it&#8217;s temporary and will be coming back in time.



<h2 class="wp-block-heading">Time Jumps</h2>



<div class="wp-block-jetpack-markdown"><ul>
<li><a href="#t=00:07">00:07</a> Alex is back!</li>
<li><a href="#t=01:10">01:10</a> The history of search at CodePen</li>
<li><a href="#t=02:15">02:15</a> Why was Elasticsearch not the right choice for CodePen?</li>
<li><a href="#t=09:36">09:36</a> Why we’re using PostGres instead</li>
<li><a href="#t=15:18">15:18</a> What does triggers have to do with search?</li>
<li><a href="#t=21:02">21:02</a> Figuring out what people are actually searching for</li>
<li><a href="#t=24:19">24:19</a> Some of the tradeoffs in changing search</li>
</ul>
</div>

Podurama

Home

Trending

Personal

Your Podcasts

New Episodes

My Files

Favourite Episodes

Tags (Folders)

Recently Played

Bookmarks

Followed Playlists

405: Elasticsearch → Postgres Search

CodePen

AI Chapters

AI Insights

Reviews