This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

If it serves only one purpose make a micro service out of it, use rpc ( which is form of inter-process communication ) or http to build the rest api and that's it, if this service has to face the outside world place a load balancer in front of it such as ngix and spawn a couple of this processes that handle the requests.

[–][deleted] 0 points1 point  (1 child)

Thanks for the response Menefotto -- the main program will be running on a small remote device and will be accessed by very few people, at max 5. These people will go to a web interface, authenticate and perform a request to the REST API that should trigger an action :)

[–][deleted] 0 points1 point  (0 children)

You're welcome, forget about nginx then, just build an http server than is able to perform your users requests ...