-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: new architecture of cubefs in the cloud #3088
Comments
Please don't abandon the local storage use case. I don't want to use cloud storage, I want to build cloud storage, and the current architecture of CubeFS is great for me. Otherwise, I fully support this. Check out JuiceFS, it does something similar. |
local storage will not be abandoned, it will continue to be optimized |
Perfect :) Then I fully support this. Let's make CubeFS more flexible 👯 |
that is a good idea. The need for file-level lifecycle management functions is crucial for cost considerations. |
正在开发的功能在哪个分支上? |
design the new architecture of running CubeFS in the cloud
Goal: "Achieving Compute-Storage Separation without Performance Degradation in the Cloud"
Describe the solution
cubefs cloud = its metadata layer (RAM) + its hot data layer (SSD) + the cold data layer in S3,
note the hot data layer = the newly written data (such as the recent WALs) + the frequently accessed data (such as a file just open and read); the cold data layer = the file extents swapped out from the hot data layer
Describe an alternate solution.
compared with direct read/write from/to S3 (and other filesystems on top of it), cubefs cloud has its very own metadata store and hot data layer for better performance to power the compute-storage separation for online database systems.
Anything else?
note by adding this feature, cubefs will become a hybrid cloud storage solution. #2994
related work: open-source filesystems on top of S3
The text was updated successfully, but these errors were encountered: