Sources
- Airbnb Engineering
- Amazon AWS AI Blog
- AWS Architecture Blog
- AWS Open Source Blog
- BrettTerpstra.com
- ByteByteGo
- CloudFlare
- Dropbox Tech Blog
- Facebook Code
- GitHub Engineering
- Google AI Blog
- Google DeepMind
- Google Open Source Blog
- HashiCorp Blog
- InfoQ
- Spotify Engineering
- Microsoft Research
- Mozilla Hacks
- Netflix Tech Blog
- NVIDIA Blog
- O'Reilly Radar
- OpenAI Blog
- SoundCloud Backstage Blog
- Stripe Blog
- The Batch | DeepLearning.AI | AI News & Insights
- The Dropbox Blog
- The GitHub Blog
- The Netflix Tech Blog
- The Official Microsoft Blog
- Vercel Blog
- Yelp Engineering and Product Blog
Engineering @ Scale — 2026-05-05#
Signal of the Day#
In an industry relentlessly pushing the separation of compute and storage, Instacart achieved a 10x write reduction and halved their search latency by doing the exact opposite: ripping out Elasticsearch and moving text/vector search directly into their Postgres transactional database. By co-locating semantic vectors with real-time inventory data using pgvector, they eliminated massive application-layer data joins and expensive overfetching, proving that bringing compute directly to the data is often the superior architectural choice for latency-sensitive operational workloads.