In general you aren't going to find a discussion in the Sling architecture of databases, in essence because the underlying JCR repository abstracts from Sling the actual persistence mechanism.
The sling launchpad application includes everything you need to run the application, there is no required external database, JackRabbit embeds a Persistence Manager that stores everything to your local file system. Check out the JackRabbit wiki for more information http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ#Available_Implementations. --- On Thu, 5/6/10, Tony Giaccone <[email protected]> wrote: From: Tony Giaccone <[email protected]> Subject: A little confused.. To: [email protected] Date: Thursday, May 6, 2010, 2:25 PM I'm trying to understand the differences between sling and jackrabbit. I understand that Jackrabbit is the underlying content repository that sling uses. As I read through the jackrabbit wiki, it seems clear that there's a database behind jackrabbit, that holds information about the documents that are being stored in the repository. However, as I read through the sling docs, there's not much that discusses the need for this database, is the because the sling distribution assumes there is a jackrabbit server installed somewhere and that part of the configuration of sling is to connect it to a JSR 170 Repository? Or is sling using some other kind of persistent store to hold document information? Tony
