- Postes vacants:
- 5 postes ouverts
- Type d'emploi désiré :
- Temps plein
- Experience :
- Débutant
- Langue :
- Anglais, Allemand
- Genre :
- Indifférent
Description de l'emploi
Bertsch Innovation is devoted to product-driven, multi-channel communication. At our European offices and at our engineering facility in Tunis, our 80+ employees develop and support our software, advise customers, and implement innovative solutions to optimize processes in the areas of product information management (PIM), digital asset management (DAM), electronic catalogues, mobile, and multi-channel publishing. We also provide customers and partners with expert training and top-quality professional services in all these areas. With more than 150 successfully implemented PIM/DAM projects and more than 600 e-CAT customers BERTSCH INNOVATION a leading medium-sized software companies in the European PIM/DAM/e-CAT/mobile sector.
Proposal : AssetStore integration with Amazon S3 (Simple Storage service)
Improved integration with Amazon S3 as asset store for mediacockpit.Mediacockpit provides an « IContentStore » inteface to support multiple backends for storing media files in our media asset management module, mediasuite.
We would like to implement a IContentStore provider that stores media files on Amozon S3. This is not too difficult in the basic form, but since many processes require file system access to the media files (asset converters e.g.ffmpeg or imagemagick, as well as publication processes and file transfer to other systems), the implementation must also support
– an intelligent local cache that stores files locally and on S3 upon initial ingest (since many processes must be run on ingest)- a cleanup process that based on a configurable ruleset and scheduler, cleans this local cache, to minimize local (redundant) storage. for example, remove files over 1MB that have not been accessed in 3 days.- for web and api clients that can access/support HTTP/TLS URLs, mediacockpit must seamlessly stream the files from S3 instead of accessing them from the local cache.- access to files in S3 must not be public, that is, the integration must create URLS that support time-bound tokens so that these URLs cannot be shared with other users (providing unauthorized access to media without mediacockpit)- for web and api clients that can access/support HTTP/TLS URLs, mediacockpit should optionally integrate with amazon cloudfront (CDN) URLs, to distribute content to end users with low latency and high data transfer speeds instead of accessing them from the standard S3 URL or the local cache. In this case, the URL may be public or private, this should be configurable in the integration intself.- the integration between mediacockpit and S3 should support the different storage tiers in S3, so a customer can define which content should land in which storage tier, including the intelligent storage tiers in S3. For example, files that are infrequently accessed get moved to Glacier. When the system accesses the files, the integration must handle the latency involved in retrieving the content.- The integration should provide the user an overview of the volume of data stored on S3 at any given time. The integration could also log / protocol all downloads from S3 or CDN to invoice the customer at a later date.
Exigences de l'emploi
Required Skills
- Good coding and documentation practices
- Good command of English
- A positive, proactive and professional attitude
- Sound analytical and problem solving skills
- Good interpersonnel and communication skills
Date d'expiration
05/03/2021