Sorry for the delay, I was finishing up my slides for JuliaCon, which incidentally address this exact topic. You can find the slides here: https://github.com/jminardi/jminardi.github.io/blob/master/files/JuliaCon-2015.pdf and I believe the video should be posted soon.
I was using ZMQ to communicate with a long running process. In Julia there was a simple loop that just listened for instructions coming in over a ZMQ socket. On Wed, Jun 17, 2015 at 1:17 PM, Matthew Krick <matt.kr...@gmail.com> wrote: > Great stuff, seems like I've still got a bunch of research to do, > especially regarding ZMQ. > > Jack, I'm really interested in your approach of using your julia process > as a separate dockerfile. Could you explain what you meant by using a ZMQ > server when you needed more communication? > > On Tuesday, June 16, 2015 at 10:35:40 AM UTC-5, Matthew Krick wrote: >> >> I've read everything I could on deployment options, but my head is still >> a mess when it comes to all the choices, especially with how fast julia is >> moving! I have a website on a node.js server & when the user inputs a list >> of points, I want to solve a traveling salesman problem (running time >> between 2 and 10 minutes, multiple users). Can someone offer some advice on >> what's worked for them or any pros/cons to each option? Least cost is >> preferable to performance. >> >> >> 1. Spawn a new node.js instance & solve using node-julia ( >> https://www.npmjs.com/package/node-julia) >> 2. Use Forio's epicenter to host the code ( >> http://forio.com/products/epicenter/) >> 3. Create a julia HTTP server & make a REST API ( >> https://github.com/JuliaWeb/HttpServer.jl) >> 4. Host on Google Compute Engine (https://cloud.google.com/compute/) >> 5. Host on Amazon's Simple Queue (http://aws.amazon.com/sqs/) >> 6. Use Julia-box, if it can somehow accept inputs via an http call ( >> https://www.juliabox.org/) >> 7. ??? >> >> >> -- Jack Minardi jack.minardi.org j...@minardi.org
