The EEF participates in many events related to the BEAM Community.
In person and online event. Tutorials 17 & 18 October
Join the major European event for Erlang and Elixir users Erlang and Elixir share the same Virtual Machine, the BEAM. This ingenious little bit of technology is perfect for fault-tolerant, resilient applications that scale to billions of users, which is one of the biggest challenges facing developers and companies today. Code BEAM has united Erlang & Elixir developers for years to grow and progress the community in the spirit of Share. Learn. Inspire.
Share Code BEAM is an event where leading developers in Erlang, Elixir and other BEAM based technologies like RabbitMQ share their use cases and success stories to allow us to grow together.
Learn We pride ourselves on our connection with community and industry leaders. At Code BEAM events you’ll be the first to learn about new frameworks and applications for the BEAM VM that can increase your productivity and help make your life easier.
Inspire We believe that now, more than ever, conferences are a great opportunity to bring your team together to meet in person and connect with like-minded people to inspire the next big idea.Learn More →
This meetup centers around the Elixir programming language and is for anyone interested in discussing Elixir and related topics. It takes a broad approach, welcoming discussion and talks on Elixir, Erlang, Phoenix Framework, as well as other community packages and projects.
Please let us know if you have an interest in presenting.
Thanks!Learn More →
In this tutorial, we will look at the steps needed to design scalable and resilient systems. The lessons learnt apply to the Erlang ecosystem, Elixir included, but are in fact technology agnostic and could be applied to most stacks, including Scala/AKKA, .net and others.
Why Learn with Erlang Solutions
Erlang Solutions are the world-leading consultants in Erlang, Elixir, RabbitMQ and technologies in the Erlang Ecosystem. We have over 20 years experience working with technologies on the BEAM VM (the virtual machine that powers Erlang and Elixir). Training and sharing knowledge is at the core of what we do. Our trainers are the same consultants that build mission critical in-production systems for some of the world’s biggest companies. Our courses are designed to deliver battle-tested methods with an eye to how the material is used in modern environments.
TARGET AUDIENCE: Software Developers and architects
DURATION: 3 hours 30 minutes
Software development experience is a must, as is an understanding of data consistency models. Experience or exposure to designing and architecting systems is a benefit, but not a prerequisite.
Distribution: This section covers how to break up your system into manageable microservices. How do you collect these microservices into nodes, which together form distributed architectural patterns, giving you your end-to-end system? What network connectivity do you use to let them communicate with each other?
Interfaces and state: This section covers how you define your service interfaces. What data and state do you distribute across your nodes, clusters, and data centres? And if requests fail across nodes, what is your recovery strategy?
Availability: You need at least two computers to make a fault-tolerant system. When dealing with fault tolerance, you have to make decisions about resilience and reliability. This section covers techniques needed to make sure your system never fails and the trade-offs you need to make in your design.
Scalability: When you picked your distributed pattern, decided how to distribute your data, and made choices on fault tolerance, resilience, and reliability, you also made trade-offs on scalability. This section covers the decisions you have to make and how they affect scalability, as well as how to deal with capacity planning, load regulation, and back pressure.
Observability: This section covers the importance of visibility on both a business level and a system level. To achieve five-nines availability, you need preemptive support and automation. To trigger automation, you need to know the state of your system and be able to react to it as quickly as possible. This includes metrics, alarms, and notifications.
The tutorial is based on the last four chapters of Designing for Scalability with Erlang/OTP by Francesco Cesarini.
ABOUT THE TRAINER
Francesco Cesarini is the founder of Erlang Solutions Ltd. He has worked with the Erlang Ecosystem on a daily basis since 1995, starting as an intern at Ericsson’s computer science laboratory. He moved on to Ericsson’s Erlang training and consulting arm working on the first release of OTP, and applying it to turnkey solutions and flagship telecom applications. In 1999, soon after Erlang was released as open source, he founded Erlang Solutions, which has become the world leader in Erlang-based consulting, contracting, training and systems development. Francesco has worked in major Erlang-based projects both within and outside Ericsson, and as Technical Director, has led the development and consulting teams at Erlang Solutions. He is also the co-author of ‘Erlang Programming’ and ‘Designing for Scalability with Erlang/OTP’ both published by O’Reilly and lectures at Oxford University.Learn More →