Server Architecture: Possible Server Configuration

Possible Server Architecture

Below are three possible server architecture scenarios to consider. In addition, see the server architecture supporting UFDC and dLOC for a working example with more server details.

Simplest Architecture

The server architecture can be as simple as a single Windows server running the SobekCM web application and the SQL database. If full-text indexing is required, an instance of Solr/Lucene can be installed on the same server as well. In this case, the entire library is self-contained in a single server.

Figure 1: Single Server SobekCM Architecture

Latency in this case will be very low and for small collections this may fit your needs, especially for collections of objects without full text. Security concerns may arise with having your database server located on your web server, although with necessary precautions most risks can be eliminated.

Division of Labor Architecture

Generally you will find that you will want more than one server for several reasons. This divides the labor between different servers. Also, this makes securing your data servers simpler, as they can be running more completely behind your firewall.

One option is to run the system over three main servers. The first server is the web server, running the SobekCM web application and containing the digital resource files for display. The second server is a database server and can also function as a caching server to limit the memory use of the web server and also lessen the load on the database itself. The third server would contain an instance of Solr/Lucene and would allow access to the Lucene text indexes for full-text searching. Again, if your library does not start with full text, it would not be necessary to utilize a Solr/Lucene server.

Figure 2: Three Server SobekCM Architecture

This architecture formed the basis of the architecture implemented to support the UF Digital Collections and the Digital Library of the Caribbean at the University of Florida for quite some time. (see below for current UFDC server architecture)

Hybrid Architecture

Of course, any combination of the architectures above may be employed, such as the architecture in Figure 3 below.

Figure 3: Hybrid SobekCM Architecture

Related Links

• Server architecture overview
• Server architecture supporting UFDC and dLOC
• Server installation instructions