From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!goblin1!goblin2!goblin.stu.neva.ru!ecngs!feeder2.ecngs.de!sequencer.elbracht.net!news6.united-newsserver.de!not-for-mail From: Michael Erdmann Subject: Re: Web Development Using Ada? Newsgroups: comp.lang.ada References: <874bf843-8212-44a4-b0c6-e20d831325bc@googlegroups.com> <51F92827.5000903@obry.net> <51f95d3a$0$14311$afc38c87@news7.united-newsserver.de> <51F97BA8.9040401@obry.net> <51f9e7e6$0$5337$afc38c87@news6.united-newsserver.de> <3ab6d365-9832-4d51-80a9-b6438930ce84@googlegroups.com> <51fbeb3e$0$81782$afc38c87@news6.united-newsserver.de> <2223020c-08d4-4533-9de5-ddd2964d373a@googlegroups.com> User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 03 Aug 2013 06:51:50 GMT Message-ID: <51fca886$0$73312$afc38c87@news6.united-newsserver.de> Organization: united-newsserver, Premium-Usenet NNTP-Posting-Date: 03 Aug 2013 08:51:50 CEST NNTP-Posting-Host: 7d5c9e6d.news6.united-newsserver.de X-Trace: DXC=D:G`F[^3S?MISQRb_LiV7Dk2IUPZ X-Complaints-To: abuse@united-newsserver.de Xref: news.eternal-september.org comp.lang.ada:16669 Date: 2013-08-03T08:51:50+02:00 List-Id: On Fri, 02 Aug 2013 13:54:42 -0700, Maciej Sobczak wrote: >> > I would not expect AWS to handle this - specialized tools like nginx ..... >> > limited resources of the Ada web-development community. >> >> Do you already have some experiences while integrating your Ada >> application on the nginx? > > Yes. There is nothing special or particular to Ada (and AWS) in this. > > The setup that we use is to have a single nginx proxy server listening > on port 80 (the "standard" HTTP port) and dispatching requests based on > the target host name (there can be many such names residing on a single > physical address) to the particular AWS server that is handling the > given service. Thanxs sounds really like a reasonable solution. I guess you have also influence on the dispatching algorithm allowing? This would allow to map different services into different host and therefor simplify the LB configuration:-) >The AWS server can be on the same or on a different > machine than the one where nginx itself runs. Is nginx aware about the availability of a specific host? >Most importantly, the AWS > server(s) does not have to listen on any privileged port number, which > makes it much easier to manage from non-root accounts. All this is > invisible to users. I checked the page of nginx.org there is not to much of documentation. By chance do you have a better link? /Michael