> For the complete documentation index, see [llms.txt](https://docs.eventoframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventoframework.com/getting-started/quick-start.md).

# Quick Start

## Evento Server

To start building a RECQ based Architecture you need a Message Gateway to handle and manage message communication between components (microservices). To do this we use [Evento Server](/evento-server/evento-server-introduction.md).

To start using Evento Server you need a [Postgres Database](https://www.postgresql.org/) and an instance of Evento Server that you can find on [Docker Hub](https://hub.docker.com/): <https://hub.docker.com/r/eventoframework/evento-server>

We have also prepared a simple docker-compose.yml to set up your development environment:

```yaml
version: '3.3'
services:
  evento-db:
    image: 'postgres:latest'
    restart: always
    environment:
      - POSTGRES_PASSWORD=secret
      - POSTGRES_DB=evento
    volumes:
      - ./data/postgres:/var/lib/postgresql/data/
  evento-server:
    image: 'eventoframework/evento-server:latest'
    restart: on-failure
    depends_on:
      - evento-db
    environment:
      # Cluster name visualized on the GUI
      - evento_cluster_name=evento-server
      # Capture rate for internal telemetry
      - evento_performance_capture_rate=1
      # Telemetry data TTL
      - evento_telemetry_ttl=365
      # Secret key used to generate JWT access tokens
      - evento_security_signing_key=MY_JWT_SECRET_TOKEN_SEED
      # Postgres Database Connection Parameters
      - spring_datasource_url=jdbc:postgresql://evento-db:5432/evento
      - spring_datasource_username=postgres
      - spring_datasource_password=secret
    ports:
      - '3000:3000'
      - '3030:3030'
```

{% hint style="info" %}
In Evento v2, bundles register themselves with the server at runtime over the message bus — there is no JAR upload and no deployment script, so no upload volume or spawn-script bind is needed. Deploying and scaling bundle instances is handled by your orchestrator (e.g. Kubernetes or Nomad).
{% endhint %}

***

## Evento Framework

To develop RECQ components you need the [Evento Framework](/evento-framework/evento-framework-introcution.md) Bundle Library.

{% hint style="danger" %}
Evento Framework v2 requires [Java 25](https://openjdk.org/projects/jdk/25/) or newer.
{% endhint %}

You can find the library on [Maven Central](https://central.sonatype.com/): <https://central.sonatype.com/artifact/com.eventoframework/evento-bundle>

#### Gradle

```gradle
implementation group: 'com.eventoframework', name: 'evento-bundle', version: '2.0.0'
```

#### Maven

```xml
<dependency>
    <groupId>com.eventoframework</groupId>
    <artifactId>evento-bundle</artifactId>
    <version>2.0.0</version>
</dependency>
```

{% hint style="info" %}
Evento framework is independent of any other structured known framework like [Spring](https://spring.io/), [Micronaut ](https://micronaut.io/)or [Quarkus](https://quarkus.io/), so you can implement a RECQ application using your preferred technology even plain [JavaEE](https://it.wikipedia.org/wiki/Jakarta_EE).
{% endhint %}

***

Tu understands how to use properly Evento Server and Evento Framework we suggest you follow our Tutorial in the next chapter.