<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development Libraries on BRYSGO</title><link>https://www.brysgo.com/categories/development-libraries/</link><description>Recent content in Development Libraries on BRYSGO</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2015 00:09:33 +0000</lastBuildDate><atom:link href="https://www.brysgo.com/categories/development-libraries/index.xml" rel="self" type="application/rss+xml"/><item><title>Graphql + Bookshelf</title><link>https://www.brysgo.com/2015/08/13/graphql-bookshelf/</link><pubDate>Thu, 13 Aug 2015 00:09:33 +0000</pubDate><guid>https://www.brysgo.com/2015/08/13/graphql-bookshelf/</guid><description>&lt;p&gt;I recently switched over the project I was working on from MongoDB to PostgreSQL.&#10;The reason for the switch is not what I&amp;rsquo;m writing to discuss, but I&amp;rsquo;ll just say&#10;that the unpredictability of mongodb was starting to become an issue in development.&#10;The thought was that if it was already difficult before the data starts pouring in,&#10;it will probably be a nightmare one the product is in use. And that meant switching&#10;from &lt;a href="https://github.com/RisingStack/graffiti-mongoose"&gt;graffiti-mongoose&lt;/a&gt;, to my own graphql database glue.&lt;/p&gt;</description></item></channel></rss>