elasticmq

![ElasticMQ](https://github.com/softwaremill/elasticmq/raw/master/banner.png)

[![Ideas, suggestions, problems, questions](https://img.shields.io/badge/Discourse-ask%20question-blue)](https://softwaremill.community/c/elasticmq)
[![ CI ](https://github.com/softwaremill/elasticmq/workflows/ElasticMQ%20tests/badge.svg)](https://github.com/softwaremill/elasticmq/actions?query=workflow%3A%22ElasticMQ+tests%22)
[![Maven Central](https://maven-badges.herokuapp.com/maven-central/org.elasticmq/elasticmq-rest-sqs_3/badge.svg)](https://maven-badges.herokuapp.com/maven-central/org.elasticmq/elasticmq-rest-sqs_3/)

# tl;dr

* in-memory message queue system
* runs stand-alone, via [Docker](https://hub.docker.com/r/softwaremill/elasticmq-native/) or embedded
* [Amazon SQS](http://aws.amazon.com/sqs/)-compatible interface
* fully asynchronous implementation, no blocking calls
* optional UI, queue persistence
* created and maintained by:

<p align="center">
  <a href="https://softwaremill.com"><img src="https://files.softwaremill.com/logo/logo.png" alt="SoftwareMill logo" height="100"></a>
</p>

# Summary

ElasticMQ is a message queue system, offering an actor-based Scala and an [SQS](http://aws.amazon.com/sqs/)-compatible
REST (query) interface.

ElasticMQ follows the semantics of SQS. Messages are received by polling the queue.
When a message is received, it is blocked for a specified amount of time (the visibility timeout).
If the message isn't deleted during that time, it will be again available for delivery.
Moreover, queues and messages can be configured to always deliver messages with a delay.

The focus in SQS (and ElasticMQ) is to make sure that the messages are delivered.
It may happen, however, that a message is delivered twice (if, for example, a client dies after receiving a message and
processing it, but before deleting). That's why clients of ElasticMQ (and Amazon SQS) should be idempotent.

As ElasticMQ implements a subset of the [SQS](http://aws.amazon.com/sqs/) query (REST) interface, it is a great SQS
alternative both for testing purposes (ElasticMQ is easily embeddable) and for creating systems which work both within
and outside of the Amazon infrastructure.

# Community

* [Issues](https://github.com/adamw/elasticmq/issues)
* [Discussions & help](https://softwaremill.community/c/elasticmq/7)

# Running locally

The easiest way to run ElasticMQ locally is with Docker Compose. Clone the repository and run:

```bash
docker compose up
```

This starts two services as defined in [`docker-compose.yaml`](docker-compose.yaml):

| Service | Port | Description |
|---------|------|-------------|
| `elasticmq` | `9324` | SQS-compatible REST API (`softwaremill/elasticmq-native`) |
| `elasticmq-ui` | `3000` | Web UI for monitoring and managing queues (`softwaremill/elasticmq-ui`) |

Once running, open **http://localhost:3000** in your browser to explore the UI — you can view queues, send messages, and monitor queue statistics in real time.

The compose fil