In the world of digital preservation, IT obsolescence is a threat often more destructive than fire or humidity. Many museums have had the bitter experience of investing heavily in "custom-built" inventory software in the 2000s, only to discover ten years later that the software no longer runs on new operating systems, and that the company that created it has gone bankrupt.
The other major trend of the 2010s was the headlong rush to the public Cloud. But entrusting the entirety of a nation's memory to the servers of foreign tech giants raises immense questions of sovereignty, not to mention the monthly hosting costs for tens of terabytes of 3D models.
The solution for a cultural institution that wants to regain control (hosting its data physically on-site, in On-Premise mode), without suffering the agonies of traditional IT maintenance, lies in a technology from the world of software engineering: containerization with Docker.
1. Understanding Containerization (Docker)
To understand the value of Docker, we must look at how applications (like an inventory database or a document search engine) were traditionally installed.
Previously, installing software on a server was like mixing the ingredients of a recipe directly in the saucepan. If you needed to install two different programs requiring incompatible versions of the same ingredient (for example, database A needs Python 2, but software B needs Python 3), the server would crash. This is dependency hell.
The Concept of the "Container"
Docker solves this problem by placing each application, with all its exact dependencies, libraries, and configuration, into a completely hermetic virtual box called a "container."
A Docker container is like a standardized shipping container. Regardless of what is inside (a complex PostgreSQL database, a Node.js API, or a 3D rendering server), the "box" always has the same shape from the outside. Major consequence: if an engineer configures an archive container on their laptop in Paris, this container will run exactly the same way, without any configuration bugs, on a local server located in the basement of a museum in Cotonou or Dakar. This is the principle of absolute portability.
2. Why Docker is Vital for "On-Premise" Archives
When a State or institution decides to repatriate its data to physical servers (On-Premise), the main challenge becomes managing those servers. Containerization transforms this challenge into a strategic advantage.
Immunity against Operating System Obsolescence
In a traditional architecture, if the server's operating system (Windows or Linux) needs to be updated, there is a huge risk of breaking the museum's inventory software. With Docker, the application is isolated in its container. You can update the physical server as many times as you want, change server brands, or change operating systems: the container will continue to run unperturbed.
Instant Resurrection (Disaster Recovery)
What happens if the museum's physical server suffers a severe hardware failure (short circuit, flood)?
In a world without Docker, reinstalling the operating system, reconfiguring the databases, finding the right passwords, and reconnecting the software can take weeks of engineering work, with a high risk of data loss.
With a Dockerized architecture (deployed via a configuration file called docker-compose.yml), the entire infrastructure is coded in a simple text file. If the server is destroyed, you simply buy a new, blank server, type a single command line (docker-compose up -d), and the museum's entire digital ecosystem rises from the ashes in a few minutes, exactly as it was configured.
3. Architecture of a Docker-based "Sovereign Node"
At Ibeji Systems, our Sovereign Node concept relies heavily on this containerized architecture. In concrete terms, when we deploy a local archive server for a Ministry of Culture, the server contains only a minimalist operating system and Docker.
Inside, several containers work in harmony:
- The Database Container (PostgreSQL): It stores all the metadata (titles, dates, provenances) according to the CIDOC-CRM standard.
- The Search Engine Container (Elasticsearch): It allows researchers to make lightning-fast queries across millions of documents.
- The S3 Storage Container (MinIO): It manages heavy files (3D digital twins, 4K videos) by mimicking the behavior of commercial Cloud services, but remaining 100% locally hosted.
- The Blockchain Authentication Container: It manages communication with the Meridian Artifact ID protocol to cryptographically certify the integrity of the files.
Each of these containers can be updated individually, without interrupting the overall service.
4. Scalability: From USB Drive to National Data Center
The other strength of containerization is its elasticity. An institution can start very modestly: a single physical server (or even a powerful desktop computer) running Docker will be enough to host the first 10,000 pieces in the collection.
However, if the government launches a massive national campaign and millions of objects are digitized, the database will be overloaded. With Docker (and its big brother orchestrator, Kubernetes), there is no need to reprogram the application. You simply add new physical servers to the network, and the orchestrator will automatically clone and distribute the containers across these new machines to spread the computational load.
Conclusion: IT in the Service of Longevity
Adopting a Docker architecture to host national archives is not just a network engineer's choice. It is a strategy for cultural longevity.
By enclosing software in portable, resilient, hardware-independent bubbles, cultural institutions free themselves from the dual toxic dependencies of our era: dependence on American Cloud vendors, and dependence on IT companies creating closed, perishable software.
The archive becomes truly sovereign: it is stored on national territory, protected from hardware hazards, and guaranteed to function for decades to come, regardless of the evolution of the servers hosting it.
Build your sovereign infrastructure with Ibeji Systems's engineers: