asmhatre/spring-data-demo
1
0
Fork 0
Code Activity

time-series: QuestDB vs InfluxDB 3 vs TimescaleDB benchmark (post 25)

Browse Source
This commit is contained in:
asmhatre
2026-10-14 18:37:47 +00:00
commit 0e631d2cfa
17 changed files with 700 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+20
View File
@@ -0,0 +1,20 @@
# spring-data-demo
Companion code for a series of posts on [ankurm.com](https://ankurm.com) covering Spring Data integrations on Spring Boot 4.1 / JDK 25. Each top-level directory is one module, one post, independently runnable.
| Module | Post | Stack |
|---|---|---|
| [`time-series/`](./time-series) | Time-Series Data in Java: QuestDB vs InfluxDB vs TimescaleDB | QuestDB 10.0.1, InfluxDB 3 Core 3.12.0, TimescaleDB 2.25.1 (PG17) |
| `mongodb/` | Spring Boot 4 with MongoDB: Spring Data MongoDB, Aggregations and Transactions | MongoDB 8 replica set, Spring Data MongoDB |
| `elasticsearch/` | Full-Text Search with Spring Data Elasticsearch on Spring Boot 4 | Elasticsearch 9, Spring Data Elasticsearch |
| `distributed-cache/` | Distributed Caching in Spring Boot: Hazelcast vs Infinispan vs Redis | Hazelcast, Infinispan, Redis |
Each module has its own `pom.xml`, a `docker-compose.yml` for its backing services, and a `docs/output/` directory holding the real, re-runnable transcripts that every number quoted in its post traces back to. There are no narrative doc chapters here — the deeper material for each post lives in accordions inside the post itself.
Build and test each module from inside its own directory, e.g.:
```bash
cd time-series
source scripts/services-up.sh # starts QuestDB, InfluxDB 3, TimescaleDB
mvn test
```