Run ArcadeDB

You can run ArcadeDB in the following ways:

  • In the cloud, by running an ArcadeDB instance on Amazon AWS, Microsoft Azure, or Google Cloud Engine.

  • On-premise, on your servers, any OS is good. You can run with Docker, Podman, Kubernetes or bare metal.

  • On x86(-64), arm(64), or any other hardware supporting a JRE (Java* Runtime Environment)

  • Embedded, if you develop with a language that runs on the JVM (Java* Virtual Machine)*

To reach the best performance, use ArcadeDB in embedded mode to reach two million insertions per second on common hardware. If you need to scale up with the queries, run a HA (high availability) configuration with at least three servers, and a load balancer in front. Run ArcadeDB with Kubernetes to have an automatic setup of servers in HA and a load balancer upfront.

Embedded

This mode is possible only if your application is running in a JVM* (Java* Virtual Machine). In this configuration ArcadeDB runs in the same JVM as your application. In this way you completely avoid the client/server communication cost (TCP/IP, marshalling/unmarshalling, etc.) If the JVM that hosts your application crashes, then also ArcadeDB would crash, but don’t worry, ArcadeDB uses a WAL to recover partially committed transactions. Your data is safe! Check the Embedded Server section.

Client-Server

This is the classic way people use a DBMS, like with relational databases. The ArcadeDB server exposes HTTP/JSON API, so you can connect to ArcadeDB from any language without even using drivers. Take a look at the API and Driver Reference chapter for more information.

High Availability (HA)

You can spin up as many ArcadeDB servers as you want to have a HA setup and scale up with queries that can be executed on any servers. ArcadeDB uses a Raft based election system to guarantee the consistency of the database. For more information look at High Availability.

Getting Started

See Installation for guides to install under Linux, MacOS, Windows. Alternatively, you can run ArcadeDB using Docker:

docker run --rm -p 2424:2424 -p 2480:2480 -p 5432:5432 \
    --name arcadedb arcadedata/arcadedb:26.5.1