gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Filer Change Data Capture (markdown)

Chris Lu 2020-11-13 13:40:19 -08:00
parent f3c7ddef1b
commit e5eb2a3613
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Filer-Change-Data-Capture.md

@ -31,10 +31,10 @@ https://github.com/chrislusf/seaweedfs/blob/master/weed/pb/filer.proto#L52
# Possible Use Cases # Possible Use Cases
This is basically event processing for files. The possible use cases are all up to your imagination. This is basically stream processing or event processing for files. The possible use cases are all up to your imagination.
* Detect new image or video files. Add versions with different resolutions. * Detect new image or video files. Add versions with different resolutions.
* A **distributed configuration distribution**: stores configuration files under a folder. Detect the configuration changes and reload. * A **distributed configuration distribution**: stores configuration files under a folder. Detect the configuration changes and reload.
* A **job queue**: upload files to a folder, and processing new files as soon as possible, and delete the processed files. * A **job queue**: upload files to a folder, and processing new files as soon as possible, and delete the processed files.
* Do-it-yourself **Data Replication or Backup**. * Do-it-yourself **Data Replication or Backup**.
* **Batch processing**: streaming data is cool, but sometimes batching is more efficient. To combine streaming and batching, you can put one batch of new data as a file and trigger the batch processing on that file.