My reason for choosing Erlang in the first place was for scalability -
I need to be able to read/write/monitor upwards of 1000 MQ and Tibco
queues simultaneously, and drive them all and present status plus
drill-down info from a central point via a Web interface. I've got
access to lots of Intel servers (if necessary) to build this. With
Erlang, the ease of scaling horizontally makes it relatively
straightforward to handle that quantity of interfaces (ignoring the
fact that they're MQ and Tibco specifically), and using Yaws would
mean that I won't have issues with scalability in data presentation.
Finally, and I haven't thought this next part through thoroughly yet,
I would also lean towards using COMET (not the COM interface project;
the Web push interface project) to push updates out to my Web clients.
Finally the app is such that it needs to be 100% reliable during
extended periods of high load, and OTP gives me the capability to
build that in fairly easily.
Bottom line is that I know Erlang would be a good fit (again, ignoring
the fact that the interfaces are MQ and Tibco), whereas I think it
would take me longer to produce a less-reliable solution in Java.
Regards
Dave M.
2008/10/15 Rapsey <>:
> I'm sure Java has what you need, so why not go through jinterface?
>>> Sergej
>> On Wed, Oct 15, 2008 at 11:31 AM, Robert Raschke <>
> wrote:
>>>> On Wed, Oct 15, 2008 at 5:52 AM, David Mitchell <>
>> wrote:
>> > Thanks Jakob and Kenneth for your responses.
>> >
>> > I need to hook Erlang to a variety of external applications (MQ, Tibco
>> > Rendezvous, Oracle), none of which have "native" Erlang interfaces but
>> > all have COM interfaces available. Comet looked like a good fit
>> > (assuming I ran Erlang on a Windows box), but based on your comments
>> > I'll look elsewhere. That probably means building a C port for MQ and
>> > Tibco, and I may be able to get away with using ODBC for Oracle.
>> >
>> > If you need any votes of support to revive COMET within Ericsson,
>> > please let me know ;->
>>>> If you don't want to use something like C#, then I can recommend Lua
>> together with LuaCOM for interfacing to COM. I would guess that it's
>> not very hard to wrap a COM interface with this and expose it to
>> Erlang through a port. Still, a little bit of work would be required.
>>>> Robby
>> _______________________________________________
>> erlang-questions mailing list
>>>>http://www.erlang.org/mailman/listinfo/erlang-questions>>> _______________________________________________
> erlang-questions mailing list
>>http://www.erlang.org/mailman/listinfo/erlang-questions>