<?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>SpringSource Team Blog &#187; Data Access</title>
	<atom:link href="http://blog.springsource.org/category/data-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.org</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Mon, 09 Jan 2012 19:03:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Countdown to Grails 2.0: Persistence</title>
		<link>http://blog.springsource.org/2011/12/05/countdown-to-grails-2-0-persistence/</link>
		<comments>http://blog.springsource.org/2011/12/05/countdown-to-grails-2-0-persistence/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 10:45:38 +0000</pubDate>
		<dc:creator>Peter Ledbrook</dc:creator>
				<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Groovy/Grails]]></category>

		<guid isPermaLink="false">http://blog.springsource.org/?p=10292</guid>
		<description><![CDATA[It&#039;s been a while since the last Countdown blog post, but the release of 2.0.0.RC3 gives me a good reason to write another. In the last post, I focused on database migration and how we are standardising on the new Database Migration Plugin. I&#039;ll be continuing on the theme of persistence here and introducing several  <a href="http://blog.springsource.org/2011/12/05/countdown-to-grails-2-0-persistence/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/12/05/countdown-to-grails-2-0-persistence/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Using Cloud Foundry Services with Spring: Part 3 &#8211; the &lt;cloud&gt; namespace</title>
		<link>http://blog.springsource.org/2011/11/09/using-cloud-foundry-services-with-spring-applications-part-3-the-cloud-namespace/</link>
		<comments>http://blog.springsource.org/2011/11/09/using-cloud-foundry-services-with-spring-applications-part-3-the-cloud-namespace/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 14:58:59 +0000</pubDate>
		<dc:creator>Thomas Risberg</dc:creator>
				<category><![CDATA[3.1]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Cloud Foundry]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Spring]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=10172</guid>
		<description><![CDATA[We saw in the previous blog post Using Cloud Foundry Services with Spring: Part 2 &#8211; Auto-reconfiguration that when you deploy a Spring application, your use of data services will be detected, and your application will automatically be re-configured to use the cloud services available to your application. This works great for simple applications and  <a href="http://blog.springsource.org/2011/11/09/using-cloud-foundry-services-with-spring-applications-part-3-the-cloud-namespace/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/11/09/using-cloud-foundry-services-with-spring-applications-part-3-the-cloud-namespace/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>New application layering and persistence choices in Spring Roo 1.2</title>
		<link>http://blog.springsource.org/2011/09/14/new-application-layering-and-persistence-choices-in-spring-roo/</link>
		<comments>http://blog.springsource.org/2011/09/14/new-application-layering-and-persistence-choices-in-spring-roo/#comments</comments>
		<pubDate>Wed, 14 Sep 2011 17:18:13 +0000</pubDate>
		<dc:creator>Stefan Schmidt</dc:creator>
				<category><![CDATA[Cloud Foundry]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Roo]]></category>
		<category><![CDATA[Spring]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=9778</guid>
		<description><![CDATA[Java enterprise applications can take many shapes and forms. Depending on their requirements, developers need to decide which specific architectural layers their application needs. Up until now, Spring Roo has taken a pragmatic approach to reduce the often unnecessary complexity introduced by service facade, repository or DAO layers. The newly-released Spring Roo 1.2.0.M1 (see announcement)  <a href="http://blog.springsource.org/2011/09/14/new-application-layering-and-persistence-choices-in-spring-roo/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/09/14/new-application-layering-and-persistence-choices-in-spring-roo/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Using Postgres on Cloud Foundry</title>
		<link>http://blog.springsource.org/2011/08/30/using-postgres-on-cloud-foundry/</link>
		<comments>http://blog.springsource.org/2011/08/30/using-postgres-on-cloud-foundry/#comments</comments>
		<pubDate>Tue, 30 Aug 2011 18:06:14 +0000</pubDate>
		<dc:creator>Thomas Risberg</dc:creator>
				<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Cloud Foundry]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Spring]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=9572</guid>
		<description><![CDATA[When the new open source Platform-as-a-Service (PaaS) offering Cloud Foundry from VMware launched earlier this year, it included a relational database service powered by MySQL along with the NOSQL options of MongoDB and Redis. One of the promises of the Open PaaS is to provide choice both in languages and frameworks you can develop with  <a href="http://blog.springsource.org/2011/08/30/using-postgres-on-cloud-foundry/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/08/30/using-postgres-on-cloud-foundry/feed/</wfw:commentRss>
		<slash:comments>25</slash:comments>
		</item>
		<item>
		<title>Countdown to Grails 2.0: Database Migrations</title>
		<link>http://blog.springsource.org/2011/08/17/countdown-to-grails-2-0-database-migrations/</link>
		<comments>http://blog.springsource.org/2011/08/17/countdown-to-grails-2-0-database-migrations/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 16:05:53 +0000</pubDate>
		<dc:creator>Peter Ledbrook</dc:creator>
				<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Groovy/Grails]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=9283</guid>
		<description><![CDATA[One of the many nice features of Grails is the way it will automatically create your database schema for you from your domain model. Admittedly it&#039;s a feature of Hibernate that Grails uses, but still, it helps you get started very quickly with database-driven web applications without having to worry about the database schema. What  <a href="http://blog.springsource.org/2011/08/17/countdown-to-grails-2-0-database-migrations/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/08/17/countdown-to-grails-2-0-database-migrations/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
		<item>
		<title>Configuring Spring and JTA without full Java EE</title>
		<link>http://blog.springsource.org/2011/08/15/configuring-spring-and-jta-without-full-java-ee/</link>
		<comments>http://blog.springsource.org/2011/08/15/configuring-spring-and-jta-without-full-java-ee/#comments</comments>
		<pubDate>Mon, 15 Aug 2011 06:00:59 +0000</pubDate>
		<dc:creator>Josh Long</dc:creator>
				<category><![CDATA[Apache Tomcat]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[IOC Container]]></category>
		<category><![CDATA[JMS]]></category>
		<category><![CDATA[Spring]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=9218</guid>
		<description><![CDATA[Spring has rich support for transaction management through its PlatformTransactionManager interface and the hierarchy of implementations. Spring&#039;s transaction support provides a consistent interface for the transactional semantics of numerous APIs. Broadly, transactions can be split into two categories: local transactions and global transactions. Local transactions are those that affect only one transaction resource. Most often,  <a href="http://blog.springsource.org/2011/08/15/configuring-spring-and-jta-without-full-java-ee/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/08/15/configuring-spring-and-jta-without-full-java-ee/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Fine-tuning Spring Data repositories</title>
		<link>http://blog.springsource.org/2011/07/27/fine-tuning-spring-data-repositories/</link>
		<comments>http://blog.springsource.org/2011/07/27/fine-tuning-spring-data-repositories/#comments</comments>
		<pubDate>Wed, 27 Jul 2011 18:37:02 +0000</pubDate>
		<dc:creator>Oliver Gierke</dc:creator>
				<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=9164</guid>
		<description><![CDATA[It&#039;s only been a few days only since we&#039;ve released Spring Data JPA 1.0 GA which is the first major version of a Spring Data project shipping with an implementation of the repository abstraction inside our Spring Data Commons module. The repository abstraction consists of three major parts: defining a repository interface, exposing CRUD methods  <a href="http://blog.springsource.org/2011/07/27/fine-tuning-spring-data-repositories/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/07/27/fine-tuning-spring-data-repositories/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Using MongoDB, Redis, Node.js, and Spring MVC in a single Cloud Foundry Application</title>
		<link>http://blog.springsource.org/2011/05/03/using-mongodb-redis-node-js-and-spring-mvc-in-a-single-cloud-foundry-application/</link>
		<comments>http://blog.springsource.org/2011/05/03/using-mongodb-redis-node-js-and-spring-mvc-in-a-single-cloud-foundry-application/#comments</comments>
		<pubDate>Tue, 03 May 2011 21:39:51 +0000</pubDate>
		<dc:creator>jbrisbin</dc:creator>
				<category><![CDATA[3.1]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Cloud Foundry]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Spring]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=8735</guid>
		<description><![CDATA[Traditionally, applications have been defined by the principle technology they use. If you&#039;re building a Spring MVC application, we call it a &#034;Java app&#034;. Since our application is primarily composed of Java components, we tend to stay in our own yards and not be terribly friendly with our neighbors until we&#039;re forced to interact with  <a href="http://blog.springsource.org/2011/05/03/using-mongodb-redis-node-js-and-spring-mvc-in-a-single-cloud-foundry-application/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/05/03/using-mongodb-redis-node-js-and-spring-mvc-in-a-single-cloud-foundry-application/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Getting Started with Redis, Spring Data &amp; Cloud Foundry</title>
		<link>http://blog.springsource.org/2011/04/27/getting-started-redis-spring-cloud-foundry/</link>
		<comments>http://blog.springsource.org/2011/04/27/getting-started-redis-spring-cloud-foundry/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 10:45:19 +0000</pubDate>
		<dc:creator>Costin Leau</dc:creator>
				<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Cloud Foundry]]></category>
		<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=8680</guid>
		<description><![CDATA[One of the drivers behind the popularity of NoSQL solutions is performance (especially) under heavy loads. Due to their data model, key value stores lead the pack, providing lightweight yet flexible means of working with data. In this entry, I am going to quickly showcase what it takes to work with a key value store  <a href="http://blog.springsource.org/2011/04/27/getting-started-redis-spring-cloud-foundry/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/04/27/getting-started-redis-spring-cloud-foundry/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Advanced Spring Data JPA &#8211; Specifications and Querydsl</title>
		<link>http://blog.springsource.org/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/</link>
		<comments>http://blog.springsource.org/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/#comments</comments>
		<pubDate>Tue, 26 Apr 2011 09:52:31 +0000</pubDate>
		<dc:creator>Oliver Gierke</dc:creator>
				<category><![CDATA[Data Access]]></category>
		<category><![CDATA[Spring Data]]></category>

		<guid isPermaLink="false">http://blog.springsource.com/?p=8587</guid>
		<description><![CDATA[In my last blog post I introduced the basic feature set of Spring Data JPA. In this post I&#039;d like to dive into some more features and how they can help you simplify data access layer implementation even further. The Spring Data repository abstraction consists of an interface based programming model, some factory classes and  <a href="http://blog.springsource.org/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/"><em>Read more...</em></a>]]></description>
		<wfw:commentRss>http://blog.springsource.org/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/feed/</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
	</channel>
</rss>

