Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt

Use this file to discover all available pages before exploring further.

The Atoti Java SDK is the native software development kit for building Atoti applications. It provides direct access to the Atoti engine and supports full control over application behavior. This page is intended for developers with experience in Java and Atoti concepts.

​
Why use the Atoti Java SDK?

The Atoti Java SDK is suitable when an application requires full control over the Atoti engine. It exposes all public engine APIs and configuration options. Key benefits include:
  • Full access to Atoti engine APIs, including user-defined metrics, prefetchers, and data loading pipelines.
  • Support for custom aggregation chains that extend standard aggregation patterns.
  • Direct configuration of server behavior, security, and deployment settings.
  • Integration with standard enterprise Java toolchains and build systems.
  • Native execution on the Java runtime without an intermediate API layer.
  • Access to performance tuning options including JVM tuning, aggregate providers, and partitioning strategies.

​
Who is the Atoti Java SDK for?

The Atoti Java SDK is designed for engineers who build and deploy Atoti applications in production. It is commonly used in financial institutions and large enterprise environments. Typical use cases include:
  • Defining the data model and semantic layer.
  • Implementing complex measures and aggregation logic.
  • Configuring data ingestion and refresh strategies.
  • Managing server configuration and security.
  • Prototyping and iterating on Atoti applications before moving to production.
The Java SDK is relevant when full engine access is required. Examples include non-linear financial metrics such as VaR, expected shortfall, xVA, or Taylor approximation P&L. It is also used when low-level performance tuning is necessary.

​
What can be built with the Atoti Java SDK?

The Atoti Java SDK can be used to build all parts of an Atoti application. Common tasks include:
  • Defining the data model, including tables, fields, and relationships.
  • Creating the semantic layer with dimensions, hierarchies, and measures.
  • Writing user-defined functions for custom metrics and aggregation logic.
  • Configuring data loading pipelines for in-memory and DirectQuery sources.
  • Setting up server configuration, security, and access control.
  • Connecting to data sources such as files, relational databases, cloud warehouses, and real-time streams.

​
What is the relationship to the Atoti Python SDK?

The Atoti Python SDK provides an alternative way to build Atoti applications. It is the recommended entry point for Python-first teams and integrates with the Python ecosystem. The Java SDK exposes all public engine APIs and is the native interface for configuring the Atoti engine. Some low-level features are only available through the Java SDK. This makes it the preferred option when advanced configuration or fine-grained engine control is required. The Python SDK is regularly extended as new Java features are made available. The choice of SDK does not affect runtime performance or reliability. Applications built with either SDK run on the same Java engine.