distributed-filesystem

Object storage for a web application

阅读更多关于 Object storage for a web application

I am currently working on a website where, roughly 40 million documents and images should be served to it's users. I need suggestions on which method is the most suitable for storing content with subject to these requirements. System should be highly available, scale-able and durable. Files have to be stored permanently and users should be able to modify them. Due to client restrictions, 3rd party object storage providers such as Amazon S3 and CDNs are not suitable. File size of content can vary from 1 MB to 30 MB. (However about 90% of the files would be less than 2 MB) Content retrieval

FileSystemWatcher vs polling to watch for file changes

阅读更多关于 FileSystemWatcher vs polling to watch for file changes

问题 I need to setup an application that watches for files being created in a directory, both locally or on a network drive. Would the FileSystemWatcher or polling on a timer would be the best option. I have used both methods in the past, but not extensively. What issues (performance, reliability etc.) are there with either method? 回答1: I have seen the file system watcher fail in production and test environments. I now consider it a convenience, but I do not consider it reliable. My pattern has

订阅 distributed-filesystem