Book Image

Mastering Elixir

By : André Albuquerque, Daniel Caixinha
Book Image

Mastering Elixir

By: André Albuquerque, Daniel Caixinha

Overview of this book

Running concurrent, fault-tolerant applications that scale is a very demanding responsibility. After learning the abstractions that Elixir gives us, developers are able to build such applications with inconceivable low effort. There is a big gap between playing around with Elixir and running it in production, serving live requests. This book will help you fll this gap by going into detail on several aspects of how Elixir works and showing concrete examples of how to apply the concepts learned to a fully ?edged application. In this book, you will learn how to build a rock-solid application, beginning by using Mix to create a new project. Then you will learn how the use of Erlang's OTP, along with the Elixir abstractions that run on top of it (such as GenServer and GenStage), that allow you to build applications that are easy to parallelize and distribute. You will also master supervisors (and supervision trees), and comprehend how they are the basis for building fault-tolerant applications. Then you will use Phoenix to create a web interface for your application. Upon fnishing implementation, you will learn how to take your application to the cloud, using Kubernetes to automatically deploy, scale, and manage it. Last, but not least, you will keep your peace of mind by learning how to thoroughly test and then monitor your application.
Table of Contents (18 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
5
Demand-Driven Processing
Index

Inspecting application behavior


At the beginning of this chapter, we learned how to collect metrics throughout our application. That's the first step to successfully maintaining an application that is running smoothly in production. By collecting metrics and periodically analyzing them, we're aware of how well our application is performing. During this analysis, we will surely spot outliers or some odd behavior from a certain function or module, which will drive us to analyze its cause.

Besides learning how to collect metrics, we've also seen how to run a remote shell that's connected to our application in production. We'll also use a remote shell to run our experiments. Note that running them in production is dangerous. Since we're using our live environment, we risk bringing the service down for our clients, either due to a careless experiment or just from the added load to the system.

While this is true, and we do recommend the greatest of care when carrying out this sort of task, we also...