adelixir.tar.gz

BeliefStructure

BeliefStructure-credo

BeliefStructure-dialyzer

BeliefStructure-inchex

BeliefStructure-coveralls

BeliefStructure-bureacrat

BeliefStructure-bh

BeliefStructure-Aliases

BeliefStructure-format

BeliefStructure-dialyzer-wrong

BeliefStructure-terraform

BeliefStructure-terraform-copy

Umbrella Projects

counter

path_alllocator

path_alllocator-copy

EchoServer-Java

Distillery

observer-copy

formatter

formatter-fixed

sasl_reports

load-testing

profiling

benchee

ecto-log-copy-copy

terraform

observer-real

terraform-postman

nifs

BeliefStructure-coveralls-copy

BeliefStructure-inchexB

Elixir is a relatively new framework but shows rapid growth due to its flexibility as a functional, concurrent, distributed programming language.

This course is a practical guide to adopting an Elixir-based technology stack for distributed web applications. Engineering managers will find helpful guides on upskilling and cross-skilling their teams, and technical leads will grasp the meaningful differences between Elixir and traditional stacks. The course moves from high-level concepts such as staffing, code management, and legacy systems to developing your Elixir environment with a walkthrough of making the functional transition, distributed Elixir, and integrating external code. You’ll wrap up with deployment and maintenance functions, assessing performance, and finalizing the application.

By the end of this course, engineering managers will be prepared to tackle the unique challenge of migrating web applications to Elixir.

Adopting Elixir for Software Engineering Leads & Managers

Logger contains four severity levels. Which one is the most severe?

Logger contains four severity levels. Which one is the most severe?

While using your application in the production mode, what do we not need to rely on `Logger` for:



While using your application in the production mode, what do we not need to rely on <code>Logger</code> for:

**(True or False)** It is extremely important to never crash the Logger nor the Logger formatter because if that happens, you’ll get nothing to help you debug the problem.

(True or False) It is extremely important to never crash the Logger nor the Logger formatter because if that happens, you’ll get nothing to help you debug the problem.

**(True or False)** For SASL reports, it is not important to guarantee that the `:sasl` application is started before the `:logger` application.

(True or False) For SASL reports, it is not important to guarantee that the <code>:sasl</code> application is started before the <code>:logger</code> application.

**(True or False)** In debugging, using `:dbg.p :all, :all` will lead to an infinite loop.

(True or False) In debugging, using <code>:dbg.p :all, :all</code> will lead to an infinite loop.

Check your understanding of making your application production-ready by taking this quiz.

Introduction

Three Adoption Stories

Concept: Team Building

Concept: Ensuring Code Consistency

Concept: Legacy Systems and Dependencies

Development: Making the Functional Transition

Development - Distributed Elixir

Development - Integrating with External Code

Production - Coordinating Deployments

Production - Metrics and Performance Expectations

Production - Making Your App Production Ready

Conclusion

Appendix

Quick Quiz on Making your Application Production Ready