Listen "405: Elasticsearch → Postgres Search"
Episode Synopsis
Alex & Chris get into a fairly recent technological change at CodePen where we ditched our Elasticsearch implementation for just using our own Postgres 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's true that we've lost the ability to do in-code search for now. But it's temporary and will be coming back in time.
Time Jumps
For the power users out there: it's true that we've lost the ability to do in-code search for now. But it's temporary and will be coming back in time.
Time Jumps
More episodes of the podcast CodePen Radio
417: Iframe Allow Attribute Saga
18/11/2025
416: Upgrading Next.js & React
05/11/2025
415: Babel Choices
28/10/2025
414: Apollo (and the Almighty Cache)
23/10/2025
413: Still indie after all these years
14/10/2025
412: 2.0 Embedded Pens
09/10/2025
411: The Power of Tree-Sitter
01/10/2025
409: Our Own Script Injection
16/09/2025
408: Proxied Third-Party JavaScript
09/09/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.