icon | description |
---|---|
starfighter-twin-ion-engine |
BoxLang can be deployed to multiple runtimes |
BoxLang has been designed with a lightweight, fast, and modular core. The operating system binary is a whopping 6MB in size. This allows us to build on top of this binary according to the deployed runtime of choice. Check out our installation methods.
The currently available runtimes are the following:
Runtime | Description | Status |
---|---|---|
OS | Bare metal runtime for any OS Java runs in | Done |
JSR-223 | Java scripting interfaces | Done |
MiniServer | A pure Java webserver built with BoxLang | Done |
Servlet WAR | A servlet capable war | Done |
CommandBox | A BoxLang engine for CommandBox | Done |
AWS Lambda | Ability to run BoxLang with AWS Lambda | Done |
Docker | BoxLang CLI, MIniServer and CommandBox images | Done |
Azure Functions | Ability to run BoxLang with Microsoft Functions | In Progress |
Android | Ability to run BoxLang in Android Devices | In Planning |
iOS | Ability to run BoxLang in iOS Devices | In Planning |
WebAssembly | Ability to run BoxLang as WebAssembly compiled code | In Planning |
The core impetus of BoxLang is to grow in a hierarchical approach to target specific runtimes with specific behavior for particular runtimes. For example, the concept of FORM, URL, or web functions and components are only available to those runtimes that offer web support.
Please note that just because a runtime is not listed here, it doesn't mean BoxLang can't run there. These are just a collection of officially supported runtimes. You can just use the core runtime and make it run ANYWHERE the JVM can be run. You can embed it now in Android, Azure, OpenWhisk, and more. However, once we have official runtimes, we will post them here.
{% hint style="success" %} All of our runtime source code can be found in our organization: https://github.com/ortus-boxlang {% endhint %}
We love our community, and if you have created custom runtimes for BoxLang, please let us know, and we will add them here.