Deprecated Content Delivery storage on the file system
Published content is stored in the Content Data Store, which is normally a database. However, SDL Tridion Sites still supports storage on a local file system (the hard disk of a Presentation server or a network-accessible hard disk) as a deprecated feature. However, if you use the local file system as your Content Data Store, you restrict the functionality of SDL Tridion Sites in many ways.
- API (RESTful)
- Content Service
- Discovery Service
- Preview Service (part of Experience Manager)
- Session-enabled Content Service
- Dynamically assembling content onto a Web page through querying and filtering
- Profiling & Personalization, which enables you to track visitors and offer them personalized content
- Intelligent navigation (taxonomies)
- Outbound E-mail (Tracking database) and Audience Manager (Subscription database)
- User-Generated Content (UGC)
Because some of these items are core software components as of SDL Web 8, a normal SDL Tridion Sites installation always requires a database. The only scenario in which you can use local file system storage is if you are upgrading an existing implementation and are continuing to use deprecated features.