The Token Approach for Architecting Flow in Elixir · rrrene
The Token Approach for Architecting Flow in Elixir 30 Apr 2018 // posted in Architecting Flow in Elixir In the last two posts we looked at the Token approach and how we can leverage metaprogramming to build pipelines and custom DSLs processing this Token. The Tokenis just a struct holding relevant data for the execution of your program: # This struct is handed down during the execution of your pro
Using Metaprogramming for Architecting Flow in Elixir · rrrene
Using Metaprogramming for Architecting Flow in Elixir 09 Apr 2018 // posted in Architecting Flow in Elixir TL;DR You can adapt the ideas presented in the last article to any kind of application. Macros can be used to build a Plug-like DSL for your specific use-case. But be careful: Use metaprogramming wisely and only where it’s a good fit. Do not try to build the “Plug for everything”. In the last
Advanced Techniques for Architecting Flow in Elixir · rrrene
Advanced Techniques for Architecting Flow in Elixir 26 Mar 2018 // posted in Architecting Flow in Elixir In the last post we explored how we can use either |> or with to model how data flows through our program. There is, however, a third concept to model flow in your applications: to hand down a “token” during the execution of your program. This token contains all the information necessary for yo
Should I Use `with` or `|>` for Architecting Flow in Elixir Programs? · rrrene
Should I Use `with` or `|>` for Architecting Flow in Elixir Programs? 10 Mar 2018 // posted in Architecting Flow in Elixir In the last post we explored how data flows through our program and why it is important to recognize that the business of software is all about new and changing requirements. We implemented a simple Mix task to convert images to a given format. We can, as indicated in the last
Architecting Flow in Elixir Programs: An Introduction · rrrene
Architecting Flow in Elixir Programs: An Introduction 30 Jan 2018 // posted in Architecting Flow in Elixir Getting the “flow” of a program is one of the first things I do when looking at open source software or joining a new project at work. The easier it is to grasp how data flows through a program, the easier it is for me as a developer to estimate the impact of changes (and the business of soft
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Designing Token APIs for Architecting Flow in Elixir · rrrene
Credo: Looking at 1.0 and beyond · rrrene
Does your company use Credo? · rrrene
