No Database Needed, Native — Tarantool as an Application Server for IoT
summary
An explanation of using Tarantool as an application server for IoT rather than as a conventional database: it defines IoT and why management systems are needed, lists functional parts (device drivers, action-scripts, timer-scripts, web UI, common bus), argues why Tarantool is suitable and why a full database is not used, and presents the implementation with architecture diagrams and code examples.
AI-written summary · about
chapters (21)
- 0:00Tarantool introduction
- 1:10What is IoT?
- 3:21IoT system challenges
- 8:35Unified management need
- 10:21Tarantool as IoT server
- 12:28Tarantool architecture
- 15:01Central bus and scripts
- 18:36Script types in Tarantool
- 21:11Real-world script example
- 22:16Device drivers in Tarantool
- 24:25Central console and logging
- 26:54Web interface development
- 28:22Unified development environment
- 31:34Logic handling and scaling
- 36:36Open-source Tarantool
- 38:07Deployment and licensing
- 41:07Long-term data storage
- 42:11Tarantool’s database role
- 44:03Event processing flow
- 47:45Data vs events model
- 49:14Performance optimization
related talks
29mTarantool as a Platform for Microservices
49mPrimary Use Cases for In-Memory DBMS Illustrated by Tarantool
56mUsing Tarantool as a Data Virtualization Platform
46mTarantool: How to Save a Million Dollars on Your DB
47mStored Procedures in NoSQL DBMSs: The Tarantool Example
38mHow to Forget About Performance Problems? Tarantool as the DBMS
51mReplication in Tarantool: Configuration and Usage
54mArchitecture of a Reliable In-MemorDBMS: the Tarantool Example
