threads - use them as much as you can

David W. Bauer Jr. <>
Tue Nov 28 21:08:51 CET 2000


The work that I am doing is replacing Java based web apps with Erlang.
And you are right, erlang is a much more suitable solution because it
allows me to handle millions of requests without doing any real work in
the application.  I simply took the inets web server, embed it in a node,
and then use it to create requests into the node.  Very slick of erlang..
because I could have apache outside of the node sending requests to inets
if I wanted. 

David


                                               ~~~  ~~  ~~~~     _o
  URL: http://www.david-bauer.com             ~~~  ~~~~ ~~    _'|<,_
                                         ~~~~ ~~~   ~~~~     (*)/ (*)



On Tue, 28 Nov 2000, Sean Hinde wrote:

#> What is "the industry" using for developing concurrent, 
#> (soft) realtime software
#> applications (like tele/datacom control systems) these days 
#> anyway? (The small
#> part of it not using Erlang, that is ;-). I guess it's C and 
#> C++ on top of a
#> multitasking OS or on top of some threaded SW platform that 
#> is the most common.
#> What other concurrent high-level languages than Erlang are 
#> being used in
#> commercial projects, if any?
#
#It is interesting that Java is being pushed very hard into the internet
#server application market. This is exactly where concurrency is nice if you
#want to have systems which are responsive and resilient to some back end
#systems slowing down.
#
#My experience of this type of thing is that even getting the concept or
#value of a multithreaded application server over to Java app guys is hard
#(denial followed by intransigence and claims of impossibility). The view
#seems to be that if it blocks you just get a faster machine - which
#demonstrates no real understanding of the timeline aspects of the overall
#application.
#
#Then you need lots of load balancing switches :) to force multithreading
#into a pool of application instances listening on different ports to get any
#throughput!
#
#EJB seems to be the big buzzword and that isn't natively multithreaded at
#all.
#
#The strength of this stuff though is the ever growing libraries of APIs to
#almost every protocol under the sun, which Erlang can't compete with off the
#shelf.
#
#Sigh..
#
#- Sean
#
#
#
#NOTICE AND DISCLAIMER:
#This email (including attachments) is confidential.  If you have received
#this email in error please notify the sender immediately and delete this
#email from your system without copying or disseminating it or placing any
#reliance upon its contents.  We cannot accept liability for any breaches of
#confidence arising through use of email.  Any opinions expressed in this
#email (including attachments) are those of the author and do not necessarily
#reflect our opinions.  We will not accept responsibility for any commitments
#made by our employees outside the scope of our business.  We do not warrant
#the accuracy or completeness of such information.
#
#




More information about the erlang-questions mailing list