Book Image

Build Your Own Web Framework in Elixir

By : Aditya Iyengar
Book Image

Build Your Own Web Framework in Elixir

By: Aditya Iyengar

Overview of this book

Elixir's functional nature and metaprogramming capabilities make it an ideal language for building web frameworks, with Phoenix being the most ubiquitous framework in the Elixir ecosystem and a popular choice for companies seeking scalable web-based products. With an ever-increasing demand for Elixir engineers, developers can accelerate their careers by learning Elixir and the Phoenix web framework. With Build Your Own Web Framework in Elixir, you’ll start by exploring the fundamental concepts of web development using Elixir. You'll learn how to build a robust web server and create a router to direct incoming requests to the correct controller. Then, you'll learn to dispatch requests to controllers to respond with clean, semantic HTML, and explore the power of Domain-Specific Languages (DSL) and metaprogramming in Elixir. You'll develop a deep understanding of Elixir's unique syntax and semantics, allowing you to optimize your code for performance and maintainability. Finally, you'll discover how to effectively test each component of your application for accuracy and performance. By the end of this book, you'll have a thorough understanding of how Elixir components are implemented within Phoenix, and how to leverage its powerful features to build robust web applications.
Table of Contents (15 chapters)
1
Part 1: Web Server Fundamentals
4
Part 2: Router, Controller, and View
10
Part 3: DSL Design

Summary

In this chapter, we started by learning what metaprogramming is and its pros and cons. We also learned that metaprogramming should be used carefully, as it makes code more complex, and outlined cases when it is okay to leverage metaprogramming.

We learned that in Elixir, metaprogramming revolves around three constructs – quoted literals, macros, and compile-time callbacks. We saw how quoted literals are Elixir’s representation of an AST, which facilitates most metaprogramming. We then learned how to use macros to inject behavior, using quoted literals in a module at compile time. We also learned that quoted literals and macros are evaluated hygienically, but var!/2 can be used to bypass the hygiene and define variables outside of the scope of a quote. We then took a look at compile-time callbacks, which are used to run tasks (or add behavior) by hooking into the compilation of a module.

We then proceeded to see how a DSL should be designed and that it should...