<story><title>PostgreSQL: Jsonb has committed</title><url>http://obartunov.livejournal.com/177247.html</url></story><parent_chain></parent_chain><comment><author>SixSigma</author><text>If, like me a moment ago, you have no idea what jsonb is; see here for a full explanation  &lt;a href=&quot;http://www.postgresql.org/message-id/E1WRpmB-0002et-MT@gemulon.postgresql.org&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.postgresql.org&amp;#x2F;message-id&amp;#x2F;E1WRpmB-0002et-MT@gemul...&lt;/a&gt;&lt;p&gt;tl;dr storing json in a way that doesn&amp;#x27;t mean repeatedly parsing it to make updates</text></comment>
<story><title>PostgreSQL: Jsonb has committed</title><url>http://obartunov.livejournal.com/177247.html</url></story><parent_chain></parent_chain><comment><author>fvt</author><text>PostgreSQL was already able to compete with Oracle&amp;#x27;s RDBMS and Microsoft&amp;#x27;s SQL Server but could soon supplant Mongo for most jobs.&lt;p&gt;It&amp;#x27;s great to know that the only required storage components nowadays could be PG and ElasticSearch (as PG&amp;#x27;s full-text search can&amp;#x27;t compete with ES), and that the former is a no-brainer to setup (on top of AWS, Rackspace, etc.) or cheap to acquire (with Heroku Postgres for example).&lt;p&gt;Good job !</text></comment>