There are a number of core concepts in Appirator. These are themselves used in building Appirator and they will also be required in creating any application or API.
At its heart, Appirator is more about object modelling than API modelling. Appirator APIs are an important aspect of an Appirator application, but they are just one part of it. Without the object model, the API would not exist.
TODO
TODO
While the Appirator console contains functionality that can be used for the development of Appirator modules and applications, it is considerably more flexible for developers to use their favourite IDE for Appirator development and to additionally link their Git repository to the associated module or application via the webhook functionality supported by the Git provider.
The request flow that occurs within Appirator can be triggered by an HTTP request or it can be triggered through an event initiated either through an internal schedule or as a reaction to another request.
Every request processed within Appirator is assigned a file system. This is done automatically and developers do not need to configure or code anything in order to acquire the file system.
The Appirator core module contains a resource class called Artifact, which contains the logic needed for uploading files and binary artifacts into the cloud storage that Appirator uses to store such artifacts.