Andrea Leopardi

Mint is a young HTTP/1 and HTTP/2 client for Elixir that aims at disrupting the status quo of HTTP clients for Erlang and Elixir. Mint is built on the idea of having a functional, data-centric client that is not backed up by a process and doesn't impose a process architecture on its users. In this talk, we'll discuss the ideas behind Mint's design and get a feel of how Mint works. We'll spend some time exploring how the low-level interface that Mint provides lets us build different abstractions on top of it that are suited for different situations.

OBJECTIVES

The talk is aimed at informing participants about;

• How to implement business solutions based on erlang processes (Genserver)
• Orchestrating Genservers and Supervisors
• Best practices for working with processes
• Debugging process related problems/bugs with adverse effect on host machine resource e.g Memory, CPU.
• How to build a game engine with Elixir.

Do you have any questions on OTP, be it Erlang, Elixir or the underlying concepts behind both? Come ask Francesco Cesarini, member of the team who released the first version of OTP (and co-author of designing for Scalability with Erlang/OTP) and Andrea Leopardi, member of the Elixir core team and longtime advocate of OTP.

Libraries are the building blocks of software. All applications I've worked with make heavy use of libraries. But who writes the libraries? In this talk, Andrea will share his perspective as a library author, and talk about library design, open source, extensibility, documentation, and people.

If you're writing a stateless web application backed up by a database, there's a good chance Elixir is a great fit. However, that's not where it shines. In this talk, we'll discuss how to architect Elixir applications in order to leverage the features of the language and of its runtime. We'll look at this both from a lower level, talking about the architecture of processes inside an Elixir application, as well as from a higher perspective of writing Elixir services and architecting systems to play Elixir's strengths. We'll see practical use cases and discuss design patterns.

AUDIENCE

Folks writing or architecting Erlang/Elixir applications that already have experience with the BEAM.

OBJECTIVES

Showing design patterns, guidelines and ideas to improve or solidify the architecture of BEAM applications.

If you are writing a stateless web application backed up by a database, there is a good chance Elixir is a great fit. However, this is not where it shines. In this talk, we will discuss how to architect Elixir applications in order to leverage the features of the language and of its runtime. We will look at this both from a lower level, talking about the architecture of processes inside an Elixir application, as well as from a higher perspective of writing Elixir services and architecting systems to play to Elixir’s strengths. We will see practical use cases and discuss design patterns.

Elixir is young, but it's not as young as it used to be. The language has been stable for a long time now, but that doesn't mean it hasn't evolved.

In this talk, Andrea will tell the story of how Elixir grew up to be what it is today. He'll talk about how the language changed to work better for the community, and how the community changed to write better Elixir. Andrea will try to guess at where this is all going next.

OBJECTIVES

This talk will get the audience to have a look at the history of Elixir and how it changed since it was born, see how the community evolved throughout the years, and how the community and the language adapted to each other.

TARGET AUDIENCE

Elixir programmers might be interested since there's a chance that they witnessed the evolution (or part of it) of the language. Erlang programmers might be interested since I will also talk about how Erlang and Elixir shaped each other in the last few years.

Elixir is young, but it's not as young as it used to be. The language has been stable for a long time now, but that doesn't mean it hasn't evolved. In this talk, I want to tell the story of how Elixir grew up to be what it is today. We'll talk about how the language changed to work better for the community, and how the community changed to write better Elixir. We'll try to guess at where this is all going next.

OBJECTIVES:

Take folks through a tour of how the Elixir language evolved and how it might keep evolving in the future.

AUDIENCE:

Anyone interested in Elixir and programming languages.