In general there should be no difference, like I mentioned a few times already.
If you’re really really worried about any performance – you cannot just assume
things and will have to measure, anything you “care enough” about.
— konrad
On 13 September 2014 at 19:28:32, Prakhyat
Hi Prakhyat,
It depends.
We provide APIs for everything in both Java and Scala.
Is it better to create actor system or actors in scala or java?
There is no better as it depends on your team, their skills and
willingness to learn.
I do think it's worth to get over the initial learning curve of
Konrad,
Thanks a lot again for your brief insights :)
We are in poc stage this will help us in deciding next steps.
There is always a confusion scala or java? You read tons of Articles,
but will end up with mixed responses.
I personally like scala for the reasons you mentioned.
We want to
Language choice should have marginal (collection conversions will happen
for example) has marginal impact on performance here.
If you really care you should benchmark things :-)
--
Cheers,
Konrad 'ktoso' Malawski
hAkker @ Typesafe
http://typesafe.com
--
Read the docs:
Konrad,
Thanks again. Will keep this in mind.
From benchmarking, did you mean, micro benchmarking using caliper or jmh?
Or benchmarking runtime performance of overall poc code? If yes, then same poc
has to be implemented separately in both scala and java, followed by
performance tests on
Team,
We are building a reactive application and planning to us akka persistence.
But we are stuck at a point where we have decide between java and scala.
Below are very important questions for my analysis.
Is it better to create actor system or actors in scala or java?
What are the
