Pavlo Baron is lead architect with codecentric AG. Starting his IT life
20 years ago by implementing a bunch of printer drivers for MS-DOS in C
and x86 Assembly, he has gained knowledge of and put in to practice a
wide variety of technologies. His first Erlang experience dates from
2005, as he evaluated a reliable technology for parallel/distributed
execution of a proprietary sequential calculation engine written in C++.
Pavlo's passion is hacking code and playing with distributed systems
and large data sets. In many cases, he would choose Erlang/OTP over some
other well known, so called enterprise adopted technologies. Pavlo is
frequent conference speaker and has written three German books:
"Erlang/OTP", "Pragmatic IT Architecture" and "Fragile Agile".

Software development is more of craftsmanship than of engineering. A good craftsman carries more tools around than just a hammer. And it's relatively inefficient to use a hammer where you need a saw. So when you take the Java ecosystem for hammer, there is still a lot of situations where a saw called Erlang would be a much better fit. In this talk you will learn these situations from concrete examples.

Talk objectives: To explain to the Java people in which cases they should prefer Erlang over Java as platform, the lingual advantages of Erlang, but also cases where they should stay with Java.Target audience: Java professionals.