Adam Lindberg
Peer Stritzinger GmbH
Senior software development professional. Experience with distributed architecture, cloud infrastructure, live operations and embedded systems. Focus on dynamic languages, test driven development and agile methods. Author of Meck, an open source mocking framework for Erlang.
Past Activities
Code BEAM Lite Munich 2018
09.00 - 17.00
GRISP training - IoT Lab with GRiSP, Bare Metal Erlang, Sensors and Actuators
- Want to learn how to run Erlang without a OS kernel?
- Want to deploy software to a small wireless embedded system?
- Want to interact with hardware such as accelerometers, thermometers, hygrometers, stepper motors and a little robot?
Then this is the course for you!
Join this full day free tutorial and learn how to create and deploy Erlang projects on the GRiSP embedded board.
Learn how to connect to GRiSP using Wi-Fi and how to interact with and write your own drivers for hardware peripherals.
We will provide access to hardware such as GRiSP boards, PMOD devices and other accessories.
Knowledge about programming is required and some basic knowledge of Erlang is a plus.
This free tutorial is limited to 10 attendees only, so book now.
This free tutorial is Sponsored by Peer Stritzinger GmbH
Code BEAM Lite Berlin
09.00 - 17.00
Hands on Embedded-Systems with GRiSP - Sensors, Actuators and Robots!
COURSE OUTLINE
The one day GRiSP tutorial will get you familiar with the GRiSP hardware boards and its capabilities running embedded Erlang and Elixir applications. We'll learn how to set up an Elixir or Erlang application for the GRiSP board, deploy it and interact with different hardware components directly from Erlang. After the tutorial, there will be a workshop where you can develop prototype embedded applications together with the group, having access to the GRiSP hardware and many sensors and actuators and we’ll also bring some robotics hardware to work with! We have tasks for every level.
Embedded Hardware will be provided and the tutorial price includes a GRiSP board to take with you.
More information at https://www.grisp.org/
AUDIENCE
- Elixir and Erlang developers who want to learn about the platform and embedded systems development
- Embedded systems engineers who want to try out Erlang or Elixir for systems
OBJECTIVES
- Learn how to use our rebar3 and mix based advanced development tools to develop embedded or IoT systems for the GRiSP board
- Interact and work with real hardware
- Develop example embedded applications together
PREREQUISITES
Programming skills in Erlang or Elixir.
Please bring your laptop. Micro USB cables and Micro SD-card readers are helpful but not necessary (we will bring some).
Code BEAM STO 2018
09.25 - 17.00
GRISP training - IoT Lab with GRiSP, Bare Metal Erlang, Sensors and Actuators
9:00 - 17:00
Want to learn how to run Erlang without a OS kernel? Want to deploy software to a small wireless embedded system? Want to interact with hardware such as accelerometers, thermometers, hygrometers, stepper motors and a little robot?
Then this is the course for you!
Join this full day course and learn how to create and deploy Erlang projects on the GRiSP embedded board. Learn how to connect to it using Wi-Fi and how to interact with and write your own drivers for hardware peripherals.
We will provide access to hardware such as GRiSP boards, PMOD devices and other accessories. You will be able to buy the GRiSP board at a discount to take home with you after the course to continue developing your projects.
Knowledge about programming is required and some basic knowledge of Erlang is a plus.
Code BEAM STO 2019
10.35 - 11.20
Erlang distribution: going beyond the fully connected mesh
In our search to improve Erlang distribution as cluster sizes grow and topologies become more dynamic, we have tried many things: prototyping solutions to ahead-of-line blocking using fragmented packages, using UDP for distribution, and experimenting with Time Sensitive Networking (TSN) for real-time Erlang in industrial settings.
We will talk about our experiences so far and build upon the work of the OTP team by experimenting with a generic behaviour to make custom Erlang distribution implementations easier.
OBJECTIVES
Give a brief overview of the history and problems with Erlang distribution, look at the current state of the art and propose areas for further work and research.
AUDIENCE
People interested in Erlang internals, improved distribution protocols and who want to participate in enhancing Erlang's distribution.
Code BEAM Lite Munich 2018
11.10 - 11.50
Evolution of GRiSP
The Erlang embedded software and hardware platform GRiSP has been out for almost two years now. Since then we have made several revisions to the hardware and used it in many commercial and educational projects. Join us for a look at the history of GRiSP, an overview of how it works, and what our plans for the next version are!
OBJECTIVES
To give an introduction and overview into the world of embedded programming with GRiSP, showcase the project and present an outlook for the future.
Code BEAM STO 2018
16.15 - 17.00
1000 nodes, large messages, we want it all! Prototype with new OTP 21 API
Distribution has always been a strong side of Erlang, but it has its own limitations. Projects with specific requirements often resort to external or application-level workarounds to circumvent them. As we want to keep using Erlang distribution even in extreme use-cases, we are focusing on fixing these issues.
We explain how the new API for custom distribution in Erlang 21 lets you build your own distribution protocol. This helps us especially to prototype our extensions to Erlang distribution to scale it better and make it more universally usable.
A well-known limitation is Head-of-Line blocking. It makes the latency of messages unpredictable and it gets even worse with mesh networks. We show the results of our prototype to fix this problem.
This prototype also is the first step to more scalability by enabling message routing between nodes. We explain how link state routing protocols work and show how one of them which is very extensibe and which we plan to use for solve routing, discovery and maybe even global process registry.