I've been researching different ways of constructing the Forge Architect DSL. There are tons of different tools and different algorithms used to lex, tokenise, and evaluate context free languages:
The term configuration management has a long history beyond software development. When applied to software, people usually refer to the implementations of:
At the beginning of April 2014, we began with an idea for some sort of futuristic platform as a service designed for microservices also known as "service oriented architecture".
Our first iteration at describing ourselves was:
Matrix - Realtime Adaptive Orchestration AI operating on Cellular Service Oriented Automata Architecture
This eventually became (mainly because of our increasing knowledge of cellular automata):
Realtime Adaptive Orchestration AI operating on Cellular Automata inspired Service Oriented Architecture
Still nobody knew what we were talking about. Therefore, upon the national Australian iAwards pitching event, we described ourselves:
An operating system for the cloud and internet of things, its primary objective is to orchestrate massive distributed infrastructure, so that it becomes self-healing, self-adapting, and self-optimising.
The Matrix was no longer just a powerful platform as a service (PAAS). It is now an orchestration as a service (OAAS).
The Matrix consists of 5 major components which are codenamed and described:
- Forge - Infrastructural Type System in a Functional Logic DSL.
- Emergence - Functional Reactive Infrastructure
- Overwatch - Online Infrastructural Telemetry
- Adaptation - Machine Learned Performance Optimisation
- Convergence - Orchestration Control Surface
In any operation, as we scale the activity, we face greater and greater amounts of complexity. At every stage, we invent new abstractions to help us manage this complexity.
It is not more command and control that we are after. Instead, we seek to decrease the amount of command and control that we need. We do this by replacing coercive command and control methods with spontaneous, self-disciplined cooperation based on low-level initiative, a commonly understood intent, mutual trust, and implicit understanding and communications. -- Chet Richards - describing the OODA loop
We plan to create Matrix as a superior abstraction for distributed infrastructure, and we believe that this has applications in the cloud of today, and the internet of things in the future.
If you're interested in such a thing, take a look at: http://siliconbeachaustralia.org/jobs/jobs/cloud-infrastructure-engineer-co-founder/