You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the current JuiceFS code, integrating a new object storage backend requires direct modifications and additions to the repository's code to handle the new object storage.
This may result in a lengthy code integration cycle and the potential to impact existing functionality. Would it be possible to optimize the code architecture and adopt a JuiceFS + External Object Storage Plugin approach?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Based on the current JuiceFS code, integrating a new object storage backend requires direct modifications and additions to the repository's code to handle the new object storage.
This may result in a lengthy code integration cycle and the potential to impact existing functionality. Would it be possible to optimize the code architecture and adopt a
JuiceFS + External Object Storage Plugin
approach?Beta Was this translation helpful? Give feedback.
All reactions