-
Notifications
You must be signed in to change notification settings - Fork 12
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] FileStorageMongoDb #1005
Comments
What exactly o you mean by SubmodelElements of type
|
Oh you're right the word blobs isn't correct. This issue wasn't very well prepared. After creating I read that there is the Yeah I could create my own I will rewrite this issue a bit to better document that is a mere feature "recommendation". |
Description
In version 1.2.0, MongoDB was introduced as a means to store AAS data in a NoSQL database. This is a significant improvement, as it enables scalable and efficient data storage.
However, MongoDB currently does not support
FileStorage
forAssetInformation.thumbnail
andSubmodelElement.Attachment
in AAS.Introducing a
FileStorageMongoDb
implementation would provide centralized file storage and a unified source for complete AAS data and files. This feature would also enable running multiple instances of FA³ST-Services with the same database, facilitating load balancing and improving scalability.Description old
The v1.2.0 MongoDB persistence does not save blobs in the database thus making it harder to use for horizontal scaling as a shared filesystem has to be used between Instances of the service. This costs performance is questionable to be safe concurrently.
This affects AAS file storage and AAS asset-information thumbnails.
It would be nice if FA³ST-Service could also save files on mongoDB.
The text was updated successfully, but these errors were encountered: