AxAp is constructed in an extremely modular fashion, using a variety of data flow (and other) mechanisms. This should enable it to be very extensible.


AxAp can take advantage of various levels of modularity. Elixir functions, modules and processes can be aggregated into sets of Erlang VM applications, running (if need be) on multiple nodes (VM instances). They can also invoke and communicate with operating system processes. Finally, using Docker containers, a virtual OS level can be added. So, we (just :-) need to pick a set of mechanisms that meets our needs.


AxAp inherits modularity mechanisms from Erlang, Elixir, and the Phoenix Framework. Most of these are based on data flow, in some fashion:

AxAp also gains access to local and Internet resources via the host operating system (e.g., Linux, OSX).


This wiki page is maintained by Rich Morin, an independent consultant specializing in software design, development, and documentation. Please feel free to email comments, inquiries, suggestions, etc!

Topic revision: r2 - 21 Aug 2016, RichMorin
This site is powered by Foswiki Copyright © by the contributing authors. All material on this wiki is the property of the contributing authors.
Foswiki version v2.1.6, Release Foswiki-2.1.6, Plugin API version 2.4
Ideas, requests, problems regarding CFCL Wiki? Send us email