I am redesigning a .NET system that stores >1000 multipage .TIF images per day for retrieval by desktop and web systems. The current system uses SQL server to store the image IDs and metadata, but the actual TIF files are stored in NTFS directories on a separate file server.
Would a NoSQL database like RavenDB be a good choice for storing the TIFs as a ‘document’, and the image ID as the key?
Images are usually written once, but read many times. I am hoping RavenDB would be a good choice for storing images since I am trying to improve the current system with:
– redundancy (using replication to automatically make another copy of the repository)
– performance (using key/value nature of the images)
– reliability (the current NTFS file system ‘database’ is error prone and fragile)
Pete,
What you are talking about is not documents, because the images are binary data.
What you can do is use RavenDB attachments feature to store those images.
Attachments can take part of replication as well.