Gain insights into adopting Elixir for web apps. Explore staffing, code management, functional transition, distributed Elixir, deployment, performance assessment, and more, for a seamless transition.

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

Work on the complete application at once and then migrate it at once.

Work on one part of the application at a time and migrate it incrementally.

Ignore the legacy application code and write a new one from scratch, creating a new application at once.

What is the best way to transform your legacy application code to a new one?

What is the best way to transform your legacy application code to a new one?

What allows you to wrap the endpoints of your application and replace them with an Elixir alternative?

What allows you to wrap the endpoints of your application and replace them with an Elixir alternative?

Run the code on a throwaway staging server with copied data so that you can get information about bugs via error logs and reports.

Run the code on a production server with copied data so that you can get information about bugs via error logs and reports.

Run the code on a throwaway staging server with original data so that you can get the original results.

Run the code on a production server with original data so that you can get final results and information about bugs via error logs and reports.

What is the best release strategy for your application?

What is the best release strategy for your application?

What hosts the multiple applications that you can develop together but test and deploy separately assuming they don't share any conflicting dependencies?

What hosts the multiple applications that you can develop together but test and deploy separately assuming they don’t share any conflicting dependencies?

**(True or False)** Every application depends on other libraries, and each dependency may depend on libraries of its own, often requiring specific versions.

(True or False) Every application depends on other libraries, and each dependency may depend on libraries of its own, often requiring specific versions.

Monoliths are single-tier applications that combine data, user interface, and control logic into a single application.

Elixir umbrellas are separate applications that live in the same repository and share common resources like dependencies.

SOA services are single-tier applications that combine data, user interface, and control logic into a single application.

Elixir umbrellas are completely independent services that are built separately and share nothing but well-defined interfaces.

SOA services are completely independent services that are built separately and share nothing but well-defined interfaces.

**(Select all that apply.)** Select the statements that are true.

(Select all that apply.) Select the statements that are true.

**(True or False)** Monoliths decouple the applications. 

(True or False) Monoliths decouple the applications.

**(True or False)** It is always safe to add dependencies, as many as you want, in your applications.

(True or False) It is always safe to add dependencies, as many as you want, in your applications.

Check your understanding of legacy systems and dependencies 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 Legacy Systems and Dependencies