<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VoltDB Blog &#187; NewSQL</title>
	<atom:link href="http://blog.voltdb.com/category/blog/newsql/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.voltdb.com</link>
	<description>VoltDB Blog</description>
	<lastBuildDate>Tue, 07 May 2013 21:53:46 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>What’s the plan?</title>
		<link>http://blog.voltdb.com/whats-the-plan-2/</link>
		<comments>http://blog.voltdb.com/whats-the-plan-2/#comments</comments>
		<pubDate>Tue, 07 May 2013 09:05:09 +0000</pubDate>
		<dc:creator>Ruth Morgenstein</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[NewSQL]]></category>

		<guid isPermaLink="false">http://blog.voltdb.com/?p=649</guid>
		<description><![CDATA[<h1 dir="ltr"></h1>
<p dir="ltr">“Why is this so slow?” Have you put your application into testing (you did this before going to production, right?) and wondered why you’re not getting VoltDB’s world-class performance? The problem might be with the SQL execution plan.</p>
<p dir="ltr">This article shows you how to look at the SQL execution plans and use the information to tune your application.</p>
<h2 dir="ltr">Getting the plans at compile time</h2>
<p>In VoltDB, you can get execution plan information when you compile your stored procedures or later, when the database is up and running. When you <a href="http://voltdb.com/docs/UsingVoltDB/BuildCompileCatalog.php">build the application catalog</a> using the <span style="font-family: 'courier new', courier;">voltdb compile</span> command, the console &#8230; <a href="http://blog.voltdb.com/whats-the-plan-2/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/whats-the-plan-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JSON in VoltDB</title>
		<link>http://blog.voltdb.com/json-support-in-voltdb/</link>
		<comments>http://blog.voltdb.com/json-support-in-voltdb/#comments</comments>
		<pubDate>Tue, 05 Feb 2013 15:00:46 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Blog]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[Building VoltDB Apps]]></category>
		<category><![CDATA[High Throughput Apps]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://blog.voltdb.com/?p=586</guid>
		<description><![CDATA[<p>VoltDB 3.0 introduces the use of <a href="http://en.wikipedia.org/wiki/JSON">JSON-encoded</a> columns to allow more flexibility in how you structure and interact with your data. New SQL functions and index capabilities let you work more naturally with JSON data while maintaining the efficiency and transactional consistency of a relational database.</p>
<p><strong>How?  A VoltDB JSON Example</strong></p>
<p>Let’s assume that you want to implement a single sign-on (SSO) application using VoltDB.  You wish to store the login session for a set of different online sites under a common username.  Each login session could hold different user state, simple data values or possibly more complex structures. Additionally, &#8230; <a href="http://blog.voltdb.com/json-support-in-voltdb/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/json-support-in-voltdb/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introducing VoltDB 3.0</title>
		<link>http://blog.voltdb.com/introducing-voltdb-3-0/</link>
		<comments>http://blog.voltdb.com/introducing-voltdb-3-0/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 14:00:59 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://blog.voltdb.com/?p=577</guid>
		<description><![CDATA[<p>The VoltDB engineering team is thrilled to announce that VoltDB 3.0 is now available!  Over the past six months we’ve added a ton of features to VoltDB 3.0. This blog post lists the highlights, but that just scratches the surface. Look for future blog posts to dive into specific areas of version 3 functionality.</p>
<p>So let’s jump into what’s new in VoltDB 3.0&#8230;</p>
<p><strong>Even Faster</strong></p>
<p>VoltDB 3.0 has lower latency and more throughput than the VoltDB v2.x release.  We spent much of the past year re-engineering the transaction coordination architecture to minimize the communication between cluster nodes during transaction processing &#8230; <a href="http://blog.voltdb.com/introducing-voltdb-3-0/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/introducing-voltdb-3-0/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Big Data Value Continuum &#8211; Part 2</title>
		<link>http://blog.voltdb.com/big-data-value-continuum-part-2/</link>
		<comments>http://blog.voltdb.com/big-data-value-continuum-part-2/#comments</comments>
		<pubDate>Thu, 14 Jun 2012 14:52:28 +0000</pubDate>
		<dc:creator>Scott Jarr</dc:creator>
				<category><![CDATA[Big Data]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[Real-time Analytics]]></category>
		<category><![CDATA[OLAP and Hadoop]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=87</guid>
		<description><![CDATA[<p>This is the second post in a two-part series entitled <em>The Big Data Value Continuum</em>.  <a title="The Big Data Value Continuum" href="http://blog.voltdb.com/big-data-value-continuum/">You can find Part 1 here.</a></p>
<p>Recall that in the world of Big Data, our fundamental assumption is that data no longer resides in a static database for its entire life.  Big data demands that we squeak out the most value from the data that we have at every stage of its lifecycle.  And, oh yeah, we&#8217;re collecting way more today than we did yesterday, so get ready for that challenge, too.</p>
<p><strong>Part 2: Putting the Pieces Together</strong></p>
<p>Let’s build on the concepts we &#8230; <a href="http://blog.voltdb.com/big-data-value-continuum-part-2/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/big-data-value-continuum-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>To Flash or Not to Flash: That is the Question</title>
		<link>http://blog.voltdb.com/to-flash-or-not-to-flash-that-is-the-question/</link>
		<comments>http://blog.voltdb.com/to-flash-or-not-to-flash-that-is-the-question/#comments</comments>
		<pubDate>Tue, 12 Jun 2012 14:46:53 +0000</pubDate>
		<dc:creator>Mike Stonebraker</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[Deployment Management]]></category>
		<category><![CDATA[Durability]]></category>
		<category><![CDATA[High Availability]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=80</guid>
		<description><![CDATA[<p>I am often asked about the value of flash memory in OLTP database applications.  This blog post discusses flash technology in this context.  First, I discuss the future of flash in general; then I turn to flash (and other future storage technologies) in the context of a main memory DBMS, such as <a href="http://www.voltdb.com/tao-volt/products-solutions.php" data-cke-saved-href="http://voltdb.com/products-services/products">VoltDB</a>.</p>
<h3>The Future of Flash</h3>
<p>Flash memory is clearly a “moving window”, since its price and performance are changing quickly.  Historically, flash could only be written a few thousand times, before it would “wear out” and have to be replaced.  This drawback seems to have been eliminated &#8230; <a href="http://blog.voltdb.com/to-flash-or-not-to-flash-that-is-the-question/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/to-flash-or-not-to-flash-that-is-the-question/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OLTP and Decision Support</title>
		<link>http://blog.voltdb.com/oltp-and-decision-support/</link>
		<comments>http://blog.voltdb.com/oltp-and-decision-support/#comments</comments>
		<pubDate>Tue, 01 May 2012 14:29:47 +0000</pubDate>
		<dc:creator>Mike Stonebraker</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Big Data]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[OLTP]]></category>
		<category><![CDATA[Real-time Analytics]]></category>
		<category><![CDATA[OLAP and Hadoop]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=62</guid>
		<description><![CDATA[<p>The purpose of this blog posting is to discuss strategies for handling decision support queries in Online Transaction Processing (OLTP) applications.  First, I want to talk about the two classes of OLTP applications that I see in the marketplace.</p>
<p>The first is the <strong>traditional </strong>OLTP market that has been present for years, and is typified by purchasing Wall Street stocks.  A collection of humans (stock brokers or end-users over the web) interact with an OLTP system to trade securities.  The brokerage house (and end users for that matter) also want to run decision support queries to learn about historical trends &#8230; <a href="http://blog.voltdb.com/oltp-and-decision-support/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/oltp-and-decision-support/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Big Data Value Continuum &#8211; Part 1</title>
		<link>http://blog.voltdb.com/big-data-value-continuum/</link>
		<comments>http://blog.voltdb.com/big-data-value-continuum/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 19:07:41 +0000</pubDate>
		<dc:creator>Scott Jarr</dc:creator>
				<category><![CDATA[Big Data]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[Real-time Analytics]]></category>
		<category><![CDATA[OLAP and Hadoop]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=56</guid>
		<description><![CDATA[<p>This is the first post in a two-part series entitled <em>The Big Data Value Continuum</em>.  <a title="The Big Data Value Continuum - Part 2" href="http://blog.voltdb.com/big-data-value-continuum-part-2/">You can find Part 2 here.</a></p>
<p>Technology markets are challenging enough to understand but, when you throw in the added noise that typically accompanies early markets, gaining real insights can be next to impossible.  It is not unusual to have ten or more vendors in a particular segment and adjacent segments, and countless products attempting to solve similar customer problems. Needless to say, tech markets are rarely clear in the beginning.</p>
<p>Big Data is just such a market today. One of the challenges we &#8230; <a href="http://blog.voltdb.com/big-data-value-continuum/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/big-data-value-continuum/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Q&amp;A from March 21 Webinar</title>
		<link>http://blog.voltdb.com/qa-march-21-webinar/</link>
		<comments>http://blog.voltdb.com/qa-march-21-webinar/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 12:39:02 +0000</pubDate>
		<dc:creator>Mike Stonebraker</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Big Data]]></category>
		<category><![CDATA[NewSQL]]></category>
		<category><![CDATA[OLTP]]></category>
		<category><![CDATA[Real-time Analytics]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=28</guid>
		<description><![CDATA[<p>Last week I gave a webinar entitled <em>OldSQL vs. NoSQL vs. NewSQL for New OLTP.</em>  If you missed the live webinar and want to view the recorded version, you&#8217;ll find it <a href="http://www.voltdb.com/dig-deeper/multimedia/webinars.php" data-cke-saved-href="http://voltdb.com/resources/webinars">here</a> (you may need to scroll down to find it).  Below is a list of questions that live webinar attendees asked, in no particular order.  If you have follow-on questions, reply to this post and I or someone else from VoltDB will answer them.<img title="&#60;--break--&#62;" src="https://voltdb.com/sites/all/modules/wysiwyg/plugins/break/images/spacer.gif" alt="&#60;--break-&#62;" data-cke-saved-src="/sites/all/modules/wysiwyg/plugins/break/images/spacer.gif" /></p>
<h3>Webinar Questions and Answers</h3>
<p>1.<em>  Does VoltDB run on Scale up NUMA like systems or is it designed primarily to run on scale out clusters?</em>&#8230; <a href="http://blog.voltdb.com/qa-march-21-webinar/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/qa-march-21-webinar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
