There are, indeed, various ways of doing so. So I suppose the choice depends a lot on your personal preferences.
I don't have much experience with the node eco-system, but node-julia may be a good option for you. The way I have settled on doing this is using using https://github.com/tanmaykm/JuliaWebAPI.jl . This allows you to very easily provide a remote callable API to any Julia function using ZMQ. I use this from Java, using a standard Java ZMQ client. Alternatively, that package also wraps the ZMQ API with a HTTP/JSON api, which you can use with any http client. Presumably, the latter might be easier to do from nodejs. Regards - Avik On Tuesday, 16 June 2015 16:35:40 UTC+1, 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. ??? > > >
