<?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; VoltDB Products</title>
	<atom:link href="http://blog.voltdb.com/category/blog/voltdb-products/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>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>Announcing VoltDB v3.0 &#8212; BETA</title>
		<link>http://blog.voltdb.com/announcing-voltdb-v3-0-beta/</link>
		<comments>http://blog.voltdb.com/announcing-voltdb-v3-0-beta/#comments</comments>
		<pubDate>Fri, 09 Nov 2012 18:36:18 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Schema]]></category>
		<category><![CDATA[VoltDB Applications]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=301</guid>
		<description><![CDATA[<p>The VoltDB Engineering Team is excited to announce the availability of the VoltDB v3.0 BETA.<br />
The following provides a brief overview and details on how you can download this very important release.<br />
<strong>What is VoltDB v3.0?</strong></p>
<p>VoltDB v3.0 offers a set of user-visible features, including new SQL, indexable column functions, improved ad hoc SQL execution performance, export enhancements, online schema changes, and a more streamlined application-development process.  Under the covers, VoltDB v3.0 includes a new transaction-coordination architecture that reduces latency and improves transaction throughput.</p>
<p>We’ve worked hard over the past six months to reduce overhead within VoltDB by streamlining transaction &#8230; <a href="http://blog.voltdb.com/announcing-voltdb-v3-0-beta/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/announcing-voltdb-v3-0-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Announcing VoltDB v3.0 &#8211; Preview Release</title>
		<link>http://blog.voltdb.com/announcing-voltdb-v30-preview-release/</link>
		<comments>http://blog.voltdb.com/announcing-voltdb-v30-preview-release/#comments</comments>
		<pubDate>Thu, 27 Sep 2012 17:41:11 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Building VoltDB Apps]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[VoltDB Applications]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=140</guid>
		<description><![CDATA[<p><strong>Announcing VoltDB v3.0 &#8211; Preview Release</strong></p>
<p>The next major release of VoltDB, version 3.0, is right around the corner.  In anticipation of this release, we’re announcing a preview release of the v3.0 offering, available immediately.  A brief overview and details on how you can preview this exciting release is found below.<br />
<strong>What is VoltDB v3.0?</strong></p>
<p>The VoltDB v3.0 release includes a set of user-visible features, including new SQL (specifically column functions), ad hoc SQL execution performance, Export enhancements, online schema changes, and a more streamlined application development process.  Under the covers, however, VoltDB v3.0 includes a new transaction coordination architecture &#8230; <a href="http://blog.voltdb.com/announcing-voltdb-v30-preview-release/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/announcing-voltdb-v30-preview-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VoltDB Explain Plan Command and Planner Testing Tool</title>
		<link>http://blog.voltdb.com/voltdb-explain-plan-command-and-planner-testing-tool/</link>
		<comments>http://blog.voltdb.com/voltdb-explain-plan-command-and-planner-testing-tool/#comments</comments>
		<pubDate>Wed, 12 Sep 2012 17:33:13 +0000</pubDate>
		<dc:creator>Douglas Patten</dc:creator>
				<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Building VoltDB Apps]]></category>
		<category><![CDATA[NoSQL]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[VoltDB Applications]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=128</guid>
		<description><![CDATA[<p>My name is Zheng Li, a UMass Lowell graduate student. I spent the summer as an internship at VoltDB. Over the summer, I primarily worked on two VoltDB features, both related to query plans. The features are:</p>
<ol>
<li>Explain plan command</li>
<li>Planner testing tool</li>
</ol>
<p>A <em>query plan </em>is an ordered set of steps used to access or modify information in a SQL relational database management system (see <a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">http</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">://</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">en</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">.</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">wikipedia</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">.</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">org</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">/</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">wiki</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">/</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">Query</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">_</a><a href="http://en.wikipedia.org/wiki/Query_plan" data-cke-saved-href="http://en.wikipedia.org/wiki/Query_plan">plan</a>).  Understanding query plans is important because the first plan chosen to execute will directly affect the query execution time. Both &#8230; <a href="http://blog.voltdb.com/voltdb-explain-plan-command-and-planner-testing-tool/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/voltdb-explain-plan-command-and-planner-testing-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VoltDB&#8217;s End of Summer Engineering Update</title>
		<link>http://blog.voltdb.com/voltdbs-end-summer-engineering-update/</link>
		<comments>http://blog.voltdb.com/voltdbs-end-summer-engineering-update/#comments</comments>
		<pubDate>Tue, 28 Aug 2012 17:27:44 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Schema]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=122</guid>
		<description><![CDATA[<p>It&#8217;s been a busy summer here at VoltDB! Since spring the VoltDB Engineering team has released VoltDB four times (we&#8217;re operating on 3 week sprints) and delivered numerous product and performance enhancements.</p>
<p>Some of the major features we&#8217;ve recently released include:</p>
<ul>
<li><strong><span style="text-decoration: underline;"><a href="http://www.voltdb.com/community/documentation.php">Pause-less rejoin</a></span></strong> of failed nodes. Failed nodes can now be rejoined to the k-safe cluster without significant impact to the operational throughput of the cluster. This feature is available in the Enterprise edition of VoltDB.</li>
</ul>
<ul>
<li>Significant <strong><span style="text-decoration: underline;"><a href="http://www.voltdb.com/community/documentation.php">performance improvements around ad hoc SQL</a></span></strong>, which is SQL executed outside of stored procedures, via the @AdHoc system procedure invocation or through </li>&#8230; <a href="http://blog.voltdb.com/voltdbs-end-summer-engineering-update/" class="read_more">Read more</a></ul>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/voltdbs-end-summer-engineering-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Programming VoltDB – Easy, Flexible and Ultra-fast!</title>
		<link>http://blog.voltdb.com/programming-voltdb-easy-flexible-and-ultra-fast/</link>
		<comments>http://blog.voltdb.com/programming-voltdb-easy-flexible-and-ultra-fast/#comments</comments>
		<pubDate>Mon, 06 Aug 2012 17:16:28 +0000</pubDate>
		<dc:creator>John Piekos</dc:creator>
				<category><![CDATA[OLTP]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Building VoltDB Apps]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[VoltDB Applications]]></category>
		<category><![CDATA[VoltDB Products/Versions]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=112</guid>
		<description><![CDATA[<p>You may believe that the only way to interact with VoltDB is through Java stored procedures.  To achieve maximum throughput, VoltDB stored procedures is the way to go.  You can achieve upwards of 100,000 transactions per second on a single node.  However, you can also achieve significant throughput by interacting with VoltDB conversationally, through ad hoc SQL statements, avoiding the need to pre-compile stored procedures.</p>
<p>This blog will discuss several approaches to interacting with VoltDB programmatically and cover the performance, in terms of transaction throughput, that you should expect with each approach.</p>
<h3><strong>Ad Hoc Query</strong></h3>
<p>To VoltDB, an <strong><em>ad hoc </em></strong>&#8230; <a href="http://blog.voltdb.com/programming-voltdb-easy-flexible-and-ultra-fast/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/programming-voltdb-easy-flexible-and-ultra-fast/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recap of VoltDB for SQL Devs Webinar</title>
		<link>http://blog.voltdb.com/recap-voltdb-sql-devs-webinar/</link>
		<comments>http://blog.voltdb.com/recap-voltdb-sql-devs-webinar/#comments</comments>
		<pubDate>Tue, 31 Jul 2012 17:14:21 +0000</pubDate>
		<dc:creator>Ben Ballard</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[OLTP]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Building VoltDB Apps]]></category>
		<category><![CDATA[Public Presentations]]></category>
		<category><![CDATA[VoltDB Applications]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=109</guid>
		<description><![CDATA[<p>We had a great turnout for the <strong><em>VoltDB for SQL Developers</em></strong> webinar on July 19th. The audience was engaged and asked many good questions.  We had attendees from all over the US, Canada and Germany.  I&#8217;d like to thank all those who attended and asked questions, and those who have contacted us since then with additional questions and feedback.</p>
<p>There were several questions in particular about partitioning and working with stored procedures, which hit upon what I think are the two most important concepts.</p>
<p><strong>Partitioning</strong> enables scalability and throughput, by distributing both data storage and transaction processing across the hardware &#8230; <a href="http://blog.voltdb.com/recap-voltdb-sql-devs-webinar/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/recap-voltdb-sql-devs-webinar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>686K TPS with Spring Framework Web App and VoltDB</title>
		<link>http://blog.voltdb.com/686k-tps-spring-framework-web-app-and-voltdb/</link>
		<comments>http://blog.voltdb.com/686k-tps-spring-framework-web-app-and-voltdb/#comments</comments>
		<pubDate>Tue, 26 Jun 2012 17:10:21 +0000</pubDate>
		<dc:creator>Andrew Wilson</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[VoltDB Benchmarks]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Benchmarking]]></category>
		<category><![CDATA[Node.js Integration]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=105</guid>
		<description><![CDATA[<p>We’ve recently put up a series of blog posts describing the components of a Spring-MVC web application, including <a href="http://www.voltdb.com/tao-volt/products-solutions.php" data-cke-saved-href="http://voltdb.com/products-services/products">VoltDB</a> as the database, that saves votes being called in for talent show contestants. Today I’ll talk about what happened when we benchmarked the Voter application on Amazon’s cloud platform.  <em>The short story – running on a suitable EC2 configuration (see details below), we achieved 686,000 TPS for a Spring-enabled application using VoltDB.</em></p>
<h3>The Benchmark Application</h3>
<p>I’ll start by summarizing the aforementioned blog posts, but you are welcome to read them:</p>
<p><a href="http://blog.voltdb.com/using-spring-schedule-annotation/" data-cke-saved-href="http://voltdb.com/company/blog/using-spring-schedule-annotation">Using the Spring @Schedule Annotation</a>, <a href="http://blog.voltdb.com/using-spring-converter-api-voltdb-data-objectsh-voltdb-data-objects/" data-cke-saved-href="http://voltdb.com/company/blog/using-spring-converter-api-voltdb-data-objects">Using the Spring Converter API </a>&#8230; <a href="http://blog.voltdb.com/686k-tps-spring-framework-web-app-and-voltdb/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/686k-tps-spring-framework-web-app-and-voltdb/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Q&amp;A from My Talk at the Hamburg Javascript Meet-up</title>
		<link>http://blog.voltdb.com/qa-my-talk-hamburg-javascript-meet/</link>
		<comments>http://blog.voltdb.com/qa-my-talk-hamburg-javascript-meet/#comments</comments>
		<pubDate>Fri, 22 Jun 2012 17:07:20 +0000</pubDate>
		<dc:creator>Henning Diedrich</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[Client Libraries]]></category>
		<category><![CDATA[High Throughput Apps]]></category>
		<category><![CDATA[Node.js Integration]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=102</guid>
		<description><![CDATA[<p>On June 18 I gave a talk to the <a href="http://www.meetup.com/hamburg-js/" data-cke-saved-href="http://www.meetup.com/hamburg-js/">Javascript meet-up group in Hamburg, Germany</a>.  It was a very enjoyable evening.   I’d like to thank Martin Kleppe for organizing the event, and the meet-up group members for investing an evening to learn more about Node.js and VoltDB.</p>
<p>The group asked some interesting questions during the Q&#38;A part of my talk and in the additional discussions afterward.  Below are some of the questions I remember, along with written responses.</p>
<table border="0" cellspacing="1" cellpadding="1">
<tbody>
<tr>
<td><strong>Q:</strong></td>
<td>What are the primary differences between VoltDB Community Edition (open source license) and Enterprise Edition (commercial license)?</td>
</tr>
<tr>
<td><strong>A:</strong></td>
<td>Aside from </td></tr></tbody>&#8230; <a href="http://blog.voltdb.com/qa-my-talk-hamburg-javascript-meet/" class="read_more">Read more</a></table>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/qa-my-talk-hamburg-javascript-meet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great Evening with the TriangleJS Meet-up Group</title>
		<link>http://blog.voltdb.com/great-evening-trianglejs-meet-group/</link>
		<comments>http://blog.voltdb.com/great-evening-trianglejs-meet-group/#comments</comments>
		<pubDate>Wed, 23 May 2012 19:14:45 +0000</pubDate>
		<dc:creator>Andrew Wilson</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[VoltDB Products]]></category>
		<category><![CDATA[High Availability]]></category>
		<category><![CDATA[High Throughput Apps]]></category>
		<category><![CDATA[Node.js Integration]]></category>

		<guid isPermaLink="false">http://newblog.voltdb.com/?p=4</guid>
		<description><![CDATA[<p>Last night I gave a talk and had an engaging conversation with the <a href="http://www.meetup.com/Triangle-JavaScript/" data-cke-saved-href="http://www.meetup.com/Triangle-JavaScript/">TriangleJS</a> meet-up group in Raleigh, NC.  I’d like to thank my hosts at <a href="http://www.webassign.com/" data-cke-saved-href="http://www.webassign.com/">WebAssign</a> for providing such a nice facility, Lucas Myers for managing the logistics of the meet-up and, most of all, the group members who invested an evening to learn more about VoltDB.</p>
<p>Although my talk was somewhat geared toward recent work we’ve done with Node.js, the follow-on discussion covered a wide range of technical topics ranging from database partitioning, single- and multi-part queries, query routing, site execution and database high availability.  It was interesting &#8230; <a href="http://blog.voltdb.com/great-evening-trianglejs-meet-group/" class="read_more">Read more</a></p>]]></description>
		<wfw:commentRss>http://blog.voltdb.com/great-evening-trianglejs-meet-group/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
