The repository shall have software technologies appropriate to the services it provides to its designated communities.

This is necessary to provide expected, contracted, secure, and persistent levels of service including: ease of ingest and dissemination through appropriate depositor and user interfaces and technologies such as upload mechanisms; on-going digital object management; preservation approaches and solutions, such as migration; and system security.

Maintenance of up-to-date Designated Community technology, expectations, and use profiles; provision of software systems adequate to support ingest and use demands; systematic elicitation of feedback regarding software and service adequacy; maintenance of a current software inventory.

The objective is to track when changes in service requirements by the designated communities require a corresponding change in the software components, when changes in ingestion policies require support for new data formats and when changes in software technology require new format migration capabilities. This can be driven by changes in access requirements (new clients that require new data formats become preferred), by changes in delivery mechanisms (new data transfer mechanisms), and changes in the number and size of archived records that require more scalable software.

APTrust performs its Mandatory Responsibilities to its Designated Community using a range of software. 

APTrust staff actively develops the web front-end software “Registry”,  as well as supporting preservation service infrastructure  “Preservation Services”, and the software developed by APTrust is released under Apache License (ASL)[1]. The recently updated system is now a loosely-coupled container based microservices architecture running on the AWS container (PaaS) platform ECS Fargate. The application is built using open source technologies, such as Go and Postgres Storage media is hosted on multiple types – Glacier, S3 – on multiple Public Clouds, in multiple US regions. 

Infrastructure is selected to best support the software architecture in as efficient and reliable a manner as possible, while remaining scalable, and portable. The current use of a microservices container based infrastructure represents an advanced cloud based use case for a growing archiving repository.