# Polyglot Matters: mimir vs qryn

**Grafana Mimir** recently turned **1 year old** so let's *congratulate our friends at Grafana!*

### Different Strokes

Grafana offers its **LGTM** Stack (**L**oki for logs, **G**rafana for visualization, **T**empo for traces, and **M**imir for metrics) splitting everything into *(very)* different projects and forcing users to puzzle them back together.

On the other hand, our **polyglot stack** [**qryn**](https://qryn.dev) does the opposite and **rejoins those functions** into one with 1**00% API compatibility** in Grafana and a solid variety of ingestion formats and query standards into a thin and fast overlay operating as a powerful and flexible traspilier on top of *OLAP databases and Cloud Storage.*

---

🥳 In their [celebratory post](https://grafana.com/blog/2023/03/27/a-year-in-mimir-massive-scale-new-metrics-formats-increased-adoption/?mdm=social), Grafana involuntarily makes a great case for the polyglot features native in [**qryn**](https://qryn.dev) **-** *born and designed to be* ***"transparently different"*** 🥳

# #1: No Need for Proxies

> *<mark>Grafana: When we launched Mimir, we focused on natively consuming Prometheus metrics. But within four months, we </mark>* [*<mark>open-sourced three write proxies</mark>*](https://github.com/grafana/mimir-proxies) *<mark> to ingest metrics for Datadog, InfluxDB, and Graphite. </mark>* [*<mark>OpenTelemetry</mark>*](https://grafana.com/docs/mimir/latest/operators-guide/configure/configure-otel-collector/?pg=blog&plcmt=body-txt&mdm=social)

![A workflow diagram shows how Prometheus metrics are sent to Mimir.](https://grafana.com/static/assets/img/blog/grafana-mimir-proxy-diagram.jpg align="left")

*TLDR; To simply ingest InfluxDB, Datadog, Opentelemetry... you need more software!*

### 🚀 *qryn to the rescue!*

*Unlike Mimir*, [**qryn**](https://qryn.dev) is designed to be **polygot** and natively ingests metrics formats from **Prometheus, InfluxDB, Datadog, Elastic, Open Telemetry** and many others.

If that's not enough the [**qryn-otel-collector**](https://github.com/metrico/otel-collector) offers hundreds of additional formats.

And since qryn is compatible with Prometheus, you can still use the Grafana Proxies if you want to compare methods and performance. Freedom of choice is the game.

# #2: Out of Order Inserts

> <mark>Grafana: With the release of </mark> [<mark>Grafana Mimir 2.2</mark>](https://grafana.com/docs/mimir/latest/release-notes/v2.2/?pg=blog&plcmt=body-txt&mdm=social) <mark> came experimental support to accept out-of-order samples. With out-of-order support, Grafana Mimir can accept time series data from any metrics system that requires old samples to be ingested. This makes Grafana Mimir </mark> [<mark>a general purpose TSDB</mark>](https://grafana.com/blog/2022/03/30/announcing-grafana-mimir/?pg=blog&plcmt=body-txt&mdm=social)<mark>,...</mark>

### 🚀 *qryn is your delorean!*

Unlike Mimir, [**qryn**](https://qryn.dev) was designed to support *out-of-order* inserts in **ClickHouse** out the box *(including JS/Edge version)* for all your Metrics, Logs and Telemetry traces.

This makes **ClickHouse + qryn** a genuine alternative to any general-purpose **TSDB**!

# #3: Less is More

Mimir only gets your metrics covered. *If you want logs, you need Loki. If you need telemetry, you need Tempo*. Each with its config, versions and various quirks.

**qryn** and **qryn.cloud** get you **everything at once**, allowing users to [*ingest Logs, Metrics and Traces with end-to-end visibility using qryn's polyglot API using data from Loki, Prometheus, Opentelemetry, InfluxDB, Elastic and many more*](https://qryn.cloud) powered by ClickHouse performance - without requiring any new language, formats, or proxies.

## Let's Get Polyglot!

Give **qryn** a try today with a [free trial at qryn.cloud](https://qryn.cloud) ❤️

[![](https://cdn.hashnode.com/res/hashnode/image/upload/v1679953101917/98cb211f-dabe-4945-8da0-017749ee0099.png align="center")](https://qryn.cloud)