From e5eb2a3613be21d0cc87b97b9928b621a10b8703 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Fri, 13 Nov 2020 13:40:19 -0800 Subject: [PATCH] Updated Filer Change Data Capture (markdown) --- Filer-Change-Data-Capture.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Filer-Change-Data-Capture.md b/Filer-Change-Data-Capture.md index 8287345..d9d9f5a 100644 --- a/Filer-Change-Data-Capture.md +++ b/Filer-Change-Data-Capture.md @@ -31,10 +31,10 @@ https://github.com/chrislusf/seaweedfs/blob/master/weed/pb/filer.proto#L52 # 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. * 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. * 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.