Interoperability
As interoperable technology, Mélodium aims to be compatible with the most common programmation languages.
Languages compatibility
| Language | Internal | Peer | Guest |
|---|---|---|---|
| Rust | ✔ | ||
| C | Planned lvl 2 | ||
| C++ | Planned lvl 2 | ||
| C# | Planned lvl 3 | Planned lvl 3 | |
| Go | Planned lvl 3 | ||
| Java | Planned lvl 3 | Planned lvl 3 | |
| JavaScript | ✔ | Planned lvl 3 | Planned lvl 3 |
| Perl | Planned lvl 3 | Planned lvl 3 | |
| PHP | Planned lvl 3 | Planned lvl 3 | |
| Python | Planned lvl 1 | Planned lvl 2 | Planned lvl 2 |
| Ruby | Planned lvl 3 | Planned lvl 3 | |
| Wasm | Planned lvl 1 | Planned lvl 2 | Planned lvl 2 |
Supports
The support of other programming languages is done with the following ways.
Internal
The language is supported internally by Mélodium, no addition required, the engine proceed itself to interpretation and execution of the designated language.
Peer
The Mélodium engine can pair with an engine of the given language, with which it interacts to get data and process treatments.
Guest
The Mélodium engine is available as library for the given language, and can be embedded in developments made with this language.
Planification
Adding support for mentioned languages is subject to planning and priorization. Levels of planning are:
- planned with known technical solution, will appear in next releases of Mélodium;
- planned with known technical feasability, need full technical solution to be designed and will appear at middle term;
- planned with simple knowledge of feasability; still need tests, proofs of concept, and integration within longterm run.
The priorization and integration of languages is done based of technical necessity, business need, and ease of implementation of the solution.