1

(2 replies, posted in Juicebox-Pro Support)

Howdy,

I am considering using Juicebox for a site with thousands of images and potentially thousands of simultaneous users. The images are stored within the Amazon S3 cloud, metadata stored on a local DB.

From what I understand we would need to :

  • Hand build code to output the config.xml file for each gallery

  • Users visiting the site would download the config.xml file locally then get the images directly from Amazon S3

I'm concerned:

  • Building an XML file of 2000 images may be very slow

  • Thousands of users downloading the XML file at once may trash the server

  • The user experience may be very slow at first as it loads the XML file for the first time

Does JuiceBox solution scale to this level (I see you support unlimited images) and how do you recommend architecting it?

Is it possible to build something similar to the Flickr connection except to our own API?

Do you have an example of a JuiceBox install with thousands of images?