Index Symbols | A | C | D | F | G | J | M | O | P | S | T | W | Y Symbols - BaseDoc - Deployment - DocList - Executor - Flow - Gateway A All the components in Jina use BaseDoc and/or DocList as the main data format for communication, making use of the different C Client D Data structures coming from docarray are the basic fundamental data structure in Jina. DocArray data structure F fastentrypoints module frameworks (Kubernetes, Docker compose) to provide more advanced and production-ready settings. They can also be directly deployed to Jina AI Cloud G get_args() (in module fastentrypoints) J jina_cli module jina_cli.autocomplete module jina_cli.known_plugins module M main() (in module fastentrypoints) (in module jina_cli) module fastentrypoints jina_cli jina_cli.autocomplete jina_cli.known_plugins O Orchestration P Pythonic S serialization capabilities of these structures. Serving T The Client connects to a Gateway or Executor and sends/receives/streams data from them. These components can be orchestrated by Jina's orchestration layer or by other container orchestration frameworks such as Kubernetes or Docker Compose. They wrap them to provide them the scalability and serving capabilities. They also provide easy translation to other orchestration This layer contains all the objects and concepts that are used to actually serve the logic and receive and respond to queries. These components are designed to be used as microservices ready to be containerized. This layer contains the components making sure that the objects (especially the Executor) are deployed and scaled for serving. W with a single command line. Y YAMLish
