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

## Things we studied in this chapter

In this chapter, we focused on legacy code. We spent most of our time working through tips and techniques for moving larger applications, but we also assessed Elixir dependencies.

The migration of any large application is a problem with both technology and people. Understanding the risk factors and getting buy-in from the beginning are critical elements. The application we move might be composed of independent services or a few monoliths. Moving a monolith means isolating different elements and moving them one section at a time.

# Things we studied in this chapter

In this chapter, we focused on legacy code. We spent most of our time working through tips and techniques for moving larger applications, but we also assessed Elixir dependencies.

The migration of any large application is a problem with both technology and people. Understanding the risk factors and getting buy-in from the beginning are critical elements. The application we move might be composed of independent services or a few monoliths. Moving a monolith means isolating different elements and moving them one section at a time.

Get a summary of what we learned about legacy systems and dependencies in this chapter.

Wrapping Up

Summary of Legacy Systems and Dependencies

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

Summary of Legacy Systems and Dependencies

Things we studied in this chapter