<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 20:19:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[php|architect Blog: The NoSQL Hype Curve is Bending]]></title>
      <guid>http://www.phpdeveloper.org/news/15653</guid>
      <link>http://www.phpdeveloper.org/news/15653</link>
      <description><![CDATA[<p>
On the php|architect blog today <i>Bill Karwin</i> has shared his thoughts on NoSQL and how, despite the popularity of it during 2010, the <a href="http://phparch.com/2010/12/29/the-nosql-hype-curve-is-bending">hype curve is bending</a> and companies are realizing it's less of the "silver bullet" they expected.
</p>
<blockquote>
The technology hype of 2010 was clearly NoSQL, which proved to be more of a brand-name than a technical term. Today in his tech blog, <a href="http://www.dzone.com/links/r/why_startups_should_not_choose_nosql.html">Bozho set out his view</a> that NoSQL is probably not a good choice for startups that don't know yet where their database and application bottlenecks are.
</blockquote>
<p>
<i>Bill</i> agrees, noting that the adoption of NoSQL technologies caused some <a href="http://www.techradar.com/news/internet/web/the-death-of-digg-is-not-exaggerated-720550">major meltdowns</a> when all things weren't properly considered. He points out that "a little knowledge is dangerous - the more little, the more dangerous" and developers should seriously consider the impact a NoSQL environment should have before jumping in head first.
</p>]]></description>
      <pubDate>Wed, 29 Dec 2010 12:58:12 -0600</pubDate>
    </item>
  </channel>
</rss>
