Replication Across Different Database Engines
summary
Describes moving parts of MySQL functionality into other systems and where MySQL’s capabilities fall short. Compares database caching in memcache with using Tarantool, explaining why memcache caching is more complex than it seems and where Tarantool outperforms memcache, plus pitfalls of offloading MySQL features into Tarantool.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:33Mamba’s architecture
- 3:40Caching with Memcache
- 5:03Secondary index challenges
- 7:28Switching to Tarantool
- 8:30Tarantool replication
- 11:06Tarantool setup
- 12:10Unique index limits
- 13:35Data type conversion
- 14:18Conclusions
- 15:26Q&A
related talks
16mHow to improve MySQL performance even with Handler Socket with replication to in-memory Tarantool
54mArchitecture of a Reliable In-MemorDBMS: the Tarantool Example
44mMySQL vs something else Evaluating alternative databases
44mMySQL vs something else Evaluating alternative databases
53mMySQL DevOps
46mTarantool: How to Save a Million Dollars on Your DB
41mAsynchronous Replication Without Censorship
55mThe Future of MySQL