ABC 2026

<aside> 🚨 DISCLAIMER: This material has been produced using various openly available online resources to enhance its quality and comprehensiveness. In creating this document, we have attempted to acknowledge the original authors and primary contributors of the sourced materials. However, due to the extensive range of resources consulted, there may be instances where some contributors should be explicitly mentioned. Should there be any concerns or complaints regarding the attribution or content of this material, please do not hesitate to contact [email protected] for resolution and clarification.

</aside>

Installing ThingsBoard using Docker (Linux or Mac OS)

ThingsBoard Cloud

The ThingsBoard Cloud is fully managed, scalable and fault-tolerant platform for IoT applications

ThingsBoard Cloud is for everyone who would like to use ThingsBoard but don’t want to host their own instance of the platform.

This demo shows how to install and start ThingsBoard using Docker on Linux or macOS.

Prerequisites

You need to have Docker installed…

Running

Depending on the database used, there are three types of ThingsBoard single-instance Docker images:

• thingsboard/tb-postgres - single instance of ThingsBoard with PostgreSQL database.

  Recommended option for small servers with at least 1GB of RAM and a minimum load (a few messages per second). 2-4GB is recommended.

• thingsboard/tb-cassandra - single instance of ThingsBoard with Cassandra database.

  It is the most performant and recommended option but requires at least 4GB of RAM. 8GB is recommended.

• thingsboard/tb - single instance of ThingsBoard with embedded HSQLDB database.

  Note: Not recommended for any evaluation or production usage and is used only for development purposes and automatic tests.

In this demo, I’ll use thingsboard/tb-postgres.

Choose ThingsBoard queue service

ThingsBoard can use various messaging systems/brokers to store messages and enable communication between ThingsBoard services. How do you choose the right queue implementation?

• In Memory queue implementation is built-in and default. It is useful for Proof of Concept (PoC) environments and is not suitable for production deployments or any sort of cluster deployments.
• Kafka is recommended for production deployments. This queue is used on most of the ThingsBoard production environments now. It is useful for both on-prem and private cloud deployments. It is also useful if you like to stay independent from your cloud provider.
• RabbitMQ is recommended if you don’t have much load and you already have experience with this messaging system.
• AWS SQS is a fully managed message queuing service from AWS. It is useful if you plan to deploy ThingsBoard on AWS.