mirror of https://gitee.com/bigwinds/arangodb
32 lines
977 B
Plaintext
32 lines
977 B
Plaintext
!CHAPTER Foxx anatomy
|
|
|
|
Each Foxx service is defined by a [JSON manifest](Manifest.md) specifying the
|
|
entry point, any scripts defined by the service, possible configuration
|
|
options and Foxx dependencies, as well as other metadata. Within a service,
|
|
these options are exposed as the [Foxx Context](Context.md).
|
|
|
|
At the heart of the Foxx framework lies the [Foxx Router](Router/README.md)
|
|
which is used to define HTTP endpoints. A service can access the database
|
|
either directly from its Context using prefixed collections or the
|
|
[ArangoDB database API](Modules.md).
|
|
|
|
While Foxx is primarily designed to be used to access the database itself,
|
|
ArangoDB also provides an [API to make HTTP requests](Modules.md) to
|
|
external services.
|
|
|
|
Finally, [Scripts](Scripts.md) can be used to perform one-off tasks, which
|
|
can also be scheduled to be performed asynchronously using the built-in
|
|
job queue.
|
|
|
|
!SECTION Development mode
|
|
|
|
TODO
|
|
|
|
!SECTION Foxx store
|
|
|
|
TODO
|
|
|
|
!SECTION Cluster-Foxx
|
|
|
|
TODO
|