Tarantool
database
Tarantool is an open source (BSD-2 clause licensed), in-memory computing platform consisting of a database and an application server. It includes a heavily optimized Lua interpreter, cooperative multitasking and non-blocking IO, persistent queues, sharding, and MySQL/PostgreSQL support.
| Release | Released | Support Status | Latest |
|---|---|---|---|
| 3.2 | 2 months and 3 weeks ago (26 Aug 2024)
|
Ends
in 1 year and 9 months (26 Aug 2026)
|
3.2.1
(28 Oct 2024)
|
| 3.1 | 7 months ago (16 Apr 2024)
|
Ends
in 1 year and 4 months (16 Apr 2026)
|
3.1.2
(26 Aug 2024)
|
| 3.0 | 11 months ago (26 Dec 2023)
|
Ends
in 1 year (26 Dec 2025)
|
3.0.2
(16 Apr 2024)
|
| 2.11 (LTS) | 1 year and 6 months ago (24 May 2023)
|
Ends
in 2 years and 6 months (24 May 2027)
|
2.11.4
(20 Aug 2024)
|
| 2.10 | 2 years and 6 months ago (22 May 2022)
|
Ended
1 year and 6 months ago (24 May 2023)
|
2.10.8
(14 Sep 2023)
|
| 2.8 | 3 years and 10 months ago (30 Dec 2020)
|
Ended
2 years and 7 months ago (25 Apr 2022)
|
2.8.4
(25 Apr 2022)
|
| 2.7 | 4 years ago (23 Oct 2020)
|
Ended
3 years ago (19 Aug 2021)
|
2.7.3
(19 Aug 2021)
|
| 2.6 | 4 years ago (17 Jul 2020)
|
Ended
3 years and 7 months ago (21 Apr 2021)
|
2.6.3
(21 Apr 2021)
|
| 2.5 | 4 years and 7 months ago (20 Apr 2020)
|
Ended
3 years and 10 months ago (30 Dec 2020)
|
2.5.3
(30 Dec 2020)
|
| 2.4 | 4 years and 10 months ago (10 Jan 2020)
|
Ended
4 years ago (22 Oct 2020)
|
2.4.3
(23 Oct 2020)
|
| 2.3 | 5 years ago (02 Aug 2019)
|
Ended
4 years ago (17 Jul 2020)
|
2.3.3
(17 Jul 2020)
|
| 2.2 | 5 years and 8 months ago (22 Mar 2019)
|
Ended
4 years and 7 months ago (20 Apr 2020)
|
2.2.3
(20 Apr 2020)
|
| 1.10 (LTS) | 6 years and 8 months ago (07 Mar 2018)
|
Ended
1 year and 6 months ago (24 May 2023)
|
1.10.15
(20 Feb 2023)
|
The Tarantool release policy is changing to become more clear and intuitive. The new policy uses a SemVer-like versioning format, and introduces a new version lifecycle with more long-time support series. This document explains the new release policy, versioning rules, and release series lifecycle.
The new release policy replaces the legacy policy for 2.x.y series since 2.10.0 release and all future series (3.x.y and so on).
Here are the most significant changes from the legacy release policy:
- The third number in the version label doesn’t distinguish between pre-release (alpha and beta) and
release versions. Instead, it is used for patch (bugfix-only) releases. Pre-release versions have
suffixes, like
3.0.0-alpha1. - In the legacy release policy,
1.10was a long-term support (LTS) series, while2.x.yhad stable releases, but wasn’t an LTS series. Now both series are long-term supported.
2.11 is the long-term support (LTS) release with four years of maintenance.
More information is available on the Tarantool website.
You should be running one of the supported release numbers listed above in the rightmost column.
$ tarantool --version
Show Product Identifiers
-
repology:
tarantool -
cpe:
cpe:/a:tarantool:tarantool -
cpe:
cpe:2.3:a:tarantool:tarantool
You can submit an improvement to this page
on GitHub
.
This page has a corresponding Talk Page.
A JSON version of this page is available at /api/tarantool.json. See the API Documentation for more information. You can subscribe to the iCalendar feed at /calendar/tarantool.ics.