Pages: 100
Published: May 2020
ISBN: pending
Edition: 1
Not Yet Printed (NYP)
Did you try turning it off and on again? The same approach that works for your household appliances can work with your software. Elixir and Erlang systems can spawn applications with even hundreds of thousands of processes without skipping a beat and perhaps the most important feature in either of these languages is OTP.
Available exclusive in partnership with our friends at grox.io
OTP is a set of libraries and APIs that enable applications with extraordinary reliability and scalability through concurrency. In the next four releases, we’ll cover the main two abstractions that make up OTP: the boundary and lifecycle layers.
In this first chapter, we’ll build a calculator application without OTP. We’ll use native processes and message passing rather than the OTP library. Using this approach, you will develop an intuition for how OTP works. Then, we’ll wrap the application in an API, and show how we might implement that API using OTP instead.
In chapter two we’ll look at communication between servers. You can think of a GenServer as a template for your code. You can fill in the blanks with callbacks, bits of code you’ll implement in your own modules. When we work with OTP, the GenServer library builds the generic lifecycle management and message loops, leaving the rest to your application.
The GenServer calls your application’s callback functions at certain specific times. When things break down, OTP just turns it off and on again!
Releases:
Available exclusive in partnership with our friends at grox.io
Pages: 100
Published: May 2020
ISBN: pending
Edition: 1
Not Yet Printed (NYP)