[erlang-questions] Using erlang instead of jmx

prasanna diwadkar pdiwadkar@REDACTED
Wed May 27 09:13:19 CEST 2015

Thanks Chandru. I am in process of doing prototype.As underlying functionality is primarily Java(for e.g. DatabaseMBean exposes methods to get database details), how easy is to switch context from Erlang to Java and vice versa?  i guess  there won't me much latency issues.


From: chandrashekhar.mullaparthi@REDACTED
Date: Wed, 27 May 2015 07:38:25 +0100
Subject: Re: [erlang-questions] Using erlang instead of jmx
To: pdiwadkar@REDACTED
CC: erlang-questions@REDACTED


Without knowing much more detail, at the very least you will get more expressive and concise code. Multithreaded Java code is not a pretty sight. At the risk of sounding like a salesman, things you will gain by using erlang in this context are:

- Smaller, more expressive code base 
- No need to worry about GC pauses/tuning
- Easier troubleshooting using the runtime trace capabilities of Erlang
- You will enjoy your coding!

I think the best way to find out for yourself is to prototype this. You may be surprised at how quickly you can build reasonably complex systems.


On 26 May 2015 at 15:34, prasanna diwadkar <pdiwadkar@REDACTED> wrote:

Hello all,I am new to erlang and trying to learn. One of the community project i am working on involves multiple java based distributed systems. Each of these system exposes its functionality through MBeans(JMX) which runs on JBoss instances. So the entire communication happens through JMX channel.I am trying to understand if Erlang is fit as communication layer here instead of JMX? (We don't face concurrency issues  here(except each MBean contains code containing locks,threads etc so lots of threads run on each JVM)! but will erlang make this kind of communication better or cleaner? 


erlang-questions mailing list



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150527/c0bfad68/attachment.htm>

More information about the erlang-questions mailing list