I really appreciate if seasoned Galaxy users, or someone from MDG, can guide me. We have developed a pretty complex application, all of it with Meteor. It does, however, depend on a multitude of other services that cannot - or seemingly cannot - exist in Galaxy at the moment. I’m talking about: PostgreSQL + PostGIS, Mongo, a tile server built in Java, Varnish (adapted for tile caching and tied to the tiler), several ETL processes (some of them written in bash) for importing files.
Do you think that the following is a setup that would reliably work with Galaxy:
The two databases to be deployed via Compose.io, in the same AWS regions as Galaxy (we plan deployments in both regions).
The tile service (together with the caching service) in AWS, in the same region as Galaxy AND the Postgres DB. Metror, the tiler, and PG need to be communicating in realtime, all the time.
The ETL processes in the same container as the Meteor app. These are simply bash or compiled excutables, that are spawned as child processes at various steps during file imports into PG.
From your experience, how are things regarding latency? If I simply put everything pertaining to one deployment in the same region, would that be ok?
Then what about security? I cannot see how I would be putting all these in the same subnet, then a reverse proxy in front of everything, and firwall the whole herd. Is there a secure alternative to this setup, short of having to install SSL certs everywhere?
I am very keen to find a way of using Galaxy with all this setup.