<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mongodb on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/mongodb/</link><description>Recent content in Mongodb on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Mar 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/mongodb/index.xml" rel="self" type="application/rss+xml"/><item><title>Rolling your own search</title><link>https://blog.vnykmshr.com/writing/rolling-your-own-search/</link><pubDate>Wed, 14 Mar 2012 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/rolling-your-own-search/</guid><description>&lt;p&gt;The shop needed catalog search. Users type something, products come back. Sounds trivial until you start building it.&lt;/p&gt;
&lt;p&gt;Our stack is Node.js, MySQL for the primary data store, MongoDB for everything else we need to go fast. The catalog lives in MySQL &amp;ndash; products, categories, attributes, prices. Normalized, relational, correct. But relational isn&amp;rsquo;t searchable. Try finding &amp;ldquo;blue cotton kurta&amp;rdquo; across five joined tables with MySQL FULLTEXT on MyISAM. It sort of works. The relevance is terrible.&lt;/p&gt;</description></item></channel></rss>