From PostgreSQL to Tarantool: Choosing When There Is No Choice
summary
Describes using message queues with unusual requirements (infinite variety of filters, Active‑Active operation, high load) and the team’s experience implementing this first on PostgreSQL, hitting its limits, and then switching to Tarantool. Discusses practical reasons for choosing Tarantool over PostgreSQL for high-performance, sharded, filter-heavy queueing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:50Queue problems in SMEV
- 14:54Why PostgreSQL didn't fit
- 20:44What is Tarantool
- 24:18Queue on Tarantool
- 33:42Summary and results
- 35:34Q&A
related talks
23mSynchronizing Data from PgSQL to Tarantool
49mPrimary Use Cases for In-Memory DBMS Illustrated by Tarantool
38mHow to Forget About Performance Problems? Tarantool as the DBMS
46mTarantool: How to Save a Million Dollars on Your DB
29mTarantool as a Platform for Microservices
47mBuilding a High-Load Application for Tarantool from Scratch
47mStored Procedures in NoSQL DBMSs: The Tarantool Example
56mUsing Tarantool as a Data Virtualization Platform