Erlang from behind the Trenches
| Erlang is a programming language designed for the Internet Age, although it pre-dates the Web. It is a language designed for multi-core computers, although it pre-dates them too. It is a "beacon language", to quote Haskell guru Simon Peyton-Jones, in that it more clearly than any other language demonstrates the benefits of concurrency-oriented programming. In this talk, Francesco will introduce Erlang from behind the trenches, looking at how its history influenced its constructs. He will be doing so from a personal perspective, with anecdotes from his time as an intern at the Ericsson computer science lab at a time when the language was being heavily influenced and later when working on the OTP R1 release. |
Prevention is better than cure (unit testing in Erlang)
| Well written unit tests are a great way to ensure the correctness of software components, document their public APIs and facilitate the refactoring of code bases. The most prominent features of EUnit - Erlang's unit testing framework will be demonstrated by example. Time permitting we'll also take a quick glance at "meck" - a mocking framework for Erlang. Talk objectives: Show how Erlang software components can be unit tested in an effective and elegant fashion. Elucidate some of the more "esoteric" EUnit constructs. Target audience: Software Developers |
| In this talk we are going to explore how to integrate the RabbitMQ messaging broker with our Erlang applications. We will do an overview of AMQP the protocol used by RabbitMQ and we will see many of the messaging concepts that can make RabbitMQ an important part of our application architecture. We will see how to install the RabbitMQ Erlang Client into our project and we will see a small producer / consumer application in action. Target audience: Software Developers |
What can be done with Java but should better be done with Erlang
| 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. Target Audience: Java Professionals |
