Skip to content

Deployment

Jump to bottom
Jérôme Beau edited this page Mar 4, 2018 · 2 revisions

Server architecture

To ensure the largest audience, Archipelago is designed as a web application. As such, its canonical deployment is to run into a web application server, which can be accessed by several web clients from any platform (PC, Mac, PDAs, etc.).

Integration architecture

An existing database can integrate with an Archipelago server in 2 ways:

  • passive: the Archipelago server retrieves (pull) the data from the database. This strategy can be motivated by various reasons:
    • no logic on the database side (just a file or a web page, typically)
    • no time, resources or will to develop an Archipelago adapter
  • active: the database sends (push) its data to the Archipelago server. This strategy can also be motivated by various reasons :
    • will to promote data sharing
    • will to gather data from other databases though the Archipelago meta layer
    • will to migrate or backup data to another database
    • will to use processes hosted by the Archipelago server
Clone this wiki locally