We just went through the same evaluation. At first we leaned towards
erlang, but finding erlang developers is hard (well so is finding
_good_ scala & clojure devs I imagine).
We ended up picking a mix of erlang and clojure. Both have their
places. Clojure is nice because it gives access to a gazillion
libraries (and as an added benefit can be deployed to existing
infrastructure and doesn't shock your pointy hair boss because you can
just say "it's a Java library") Also clojure is nice because we use
Lisp in other places (LFE see below). Clojure is also nice because it
fits well into our mindset with erlang, ruby and other "low ceremony"
languages.
We also write some of our stuff in LFE (lisp flavored erlang) which
gives the ability to write a lisp compiled to the erlang vm. LFE
looks like this:
(define (start)
(: lists foreach
(lambda (a)
(case (: application start a)
('ok 'ok)
((tuple 'error (tuple 'already_started _)) 'ok)))
'(crypto ssl inets ecouch)))
Erlang is teh awesome - but not for everything. Need an IMAP
library? While JavaMail sits there taunting, you you would have to
write your own by hand in Erlang. Who wants to shave that Yak? not
me. Need a full-text search library in Erlang? same thing. It's bare
metal awesome sauce for the right problem (mostly awesome easy
clustering, messaging and network services) but it doesn't fit
everywhere.
Thankfully, you can mix the two easily with a combination of messaging
(rabbitmq/json) between the two worlds and semi-direct calls with
erlang's port system (where erlang can call out directly to Java -
it's easy). So you can use Erlang for you messaging backbone and call
out to other languages. Engine Yard (Ruby guys) are doing this with
Vertebrae and PowerSet did it with Fuzed.
-Tim
On Apr 15, 9:34 am, Aaron Feng <aaron.f...@gmail.com> wrote:
> Hi,
>
> I work for a large financial software company, and we are interested
> in using Clojure for our new project. Due to the concurrent nature of
> the project, we are evaluating three possible languages: Erlang,
> Scala, and Clojure. This project will be a hosted solution, but
> availability and performance is very important to us. We want to
> deploy the project within 6 to 12 months, but the project will
> continue to build out the rest of the functionality for the next 2 to
> 4 years. We guesstimate that it will receive around 1M hits daily
> initially, and it will continue to grow on a monthly basis.
>
> Due to the nature of the project, I'm only allowed to give high level
> overview of the project at this time.
>
> We have a bias toward Scala and Clojure because they run on top of
> JVM. The richness of existing 3rd party and open source libraries are
> also attractive for us.
>
> The fundamental question for us is: Is Clojure worth our investment
> in the current state? What are the possible risks?
>
> Also, if anyone has any thoughts on hiring Clojure people, it would be
> greatly appreciated.
>
> Thanks,
>
> Aaron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
