Use S3 for externalization of outputs

Our content stores (currently DB2) are growing through more and bigger outputs from reports although we have a rigid housekeeping. But in any case, we are limited to a certain content store size. And database storage is very expensive. File externalization is not an option. We also cannot enable new features like data sets for our customers because this would further increase content store size.

The idea is to externalize outputs from reports and datasets to a (cheap) S3 cloud storage where size and amout of data almost doesn't matter.

Another advantage of this idea is the easy reuse of output files, for example in a use case where Cognos results should be exported in csv format. For this it would be beneficial when there is a (configurable) metadata file in S3 for each output file.

The connection between Cognos and the S3 must be a strong connection and the output must be further downloadable and accessible via Cognos. The user or the SDK/REST API application should not notice that there is a S3 instead of a DB2 database in the background.

The current implementation of S3 cloud storage has some disadvantages and the connection is not strong. It's more like a "fire-and-forget" approach and files with the same name will be overwritten which is a no-go for content store externalization.

Needed By

Yesterday (Let's go already!)

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Use S3 for externalization of outputs