u/curious-techoo0

i'm working on multi-tenant application and i am trying to figure out whether tenants should be hosted in a shared dB(with tenant IDs) or in saperate databases.. can anybody tell me which one would be better and why? I would love insights from people who have dealt with multi-tenant architectures in prodiuction :)

If there are thousands of devices how do I create them? Isn't it risky what if a device gets the wrong certificates as it is unique? I'm working on ThingsBoard auto provisioning rn and can't figure out how to implement it if there are thousands of devices.. I need help :(

I'm currently working on ThingsBoard and I'm figuring out how to create certs in bulk and then flash it on the device.. Like I was wondering even thought intermediate certificate is presented to the ui.. I have to create thousands of related certs and keys right.. And then as it is unique.. Isn't it risky to flash to each respective device? What if it goes wrong? Or wrong certs are flashed? I would love insights :(

Do you think ThingsBoard CE can handle 500 devices effortlessly .. will the dashboard have issues? What perfomances are available in PE that are not in CE? At which point should i switch to PE? I'm having trouble getting a solution.. Any advice and suggestions from people who have scaled in similar IoT platforms would be very helpful :)

I'm considering switching ThingsBoard to a microservices architecture. My setup will have approximately 20000 devices, each sending telemetry every 5-10 minutes. What are the cons of moving to microservices in this scenario? Is it worth the added complexity given in the data rate? Any advice or lessons from scaling ThingsBoard(or similar IoT platforms) with microservices would be really helpful.

I'm trying to enable MQTT over TLS on port 8883 on a self-hosted ThingsBoard created on Ubuntu and running on Amazon Lightsail. As soon as I enable the below given commands..it shows this error: "Caused by: java.lang.RuntimeException:
MQTT SSL Credentials: Invalid SSL credentials configuration.
None of the PEM or KEYSTORE configurations can be used!"
but when these commands are turned off, everything works fine. I'm not able to enable 8883. MQTT port 1883 works fine when these commands are turned off.. otherwise the website goes down.
where am i going wrong?? I would love insights :(

MQTT_SSL_ENABLED=true
MQTT_SSL_BIND_PORT=8883
MQTT_SSL_PROTOCOL=TLSv1.2
MQTT_SSL_CREDENTIALS_TYPE=PEM
MQTT_SSL_PEM_CERT=/config/server_chain.pem
MQTT_SSL_PEM_KEY=/config/server.key

MQTT_SSL_ENABLED=true
MQTT_SSL_BIND_PORT=8883
MQTT_SSL_PROTOCOL=TLSv1.2
MQTT_SSL_CREDENTIALS_TYPE=PEM
MQTT_SSL_PEM_CERT=/config/server_chain.crt
MQTT_SSL_PEM_KEY=/config/server.key

I'm trying to enable MQTT over TLS on port 8883 on a self-hosted ThingsBoard created on Ubuntu and running on Amazon Lightsail. As soon as I enable the above commands..it shows this error: "Caused by: java.lang.RuntimeException:
MQTT SSL Credentials: Invalid SSL credentials configuration.
None of the PEM or KEYSTORE configurations can be used!"
but when these commands are turned off, everything works fine. I'm not able to enable 8883. MQTT port 1883 works fine when these commands are turned off.. otherwise the website goes down.
where am i going wrong?? I would love insights :(

I'm trying to enable MQTT over TLS on port 8883 on a self-hosted ThingsBoard created on Ubuntu and running on Amazon Lightsail. As soon as I enable the following port:
MQTT_SSL_ENABLED=true
MQTT_SSL_BIND_PORT=8883
MQTT_SSL_PROTOCOL=TLSv1.2
MQTT_SSL_CREDENTIALS_TYPE=PEM
MQTT_SSL_PEM_CERT=/config/server_chain.pem
MQTT_SSL_PEM_KEY=/config/server.key
it shows this error: "Caused by: java.lang.RuntimeException:
MQTT SSL Credentials: Invalid SSL credentials configuration.
None of the PEM or KEYSTORE configurations can be used!"
but when these commands are turned off, everything works fine. I'm not able to enable 8883. MQTT port 1883 works fine when these commands are turned off.. otherwise the website goes down.
where am i going wrong?? I would love insights :(

I'm trying to connect a device to a company-hosted ThingsBoard instance using X.509 authentication.

What I know:

• Access Token authentication works on MQTT port 1883.
• Device credentials have been changed to X.509 Certificate.
• I generated a client certificate and uploaded the PEM certificate to the device credentials.
• MQTTX and Python are configured with the client certificate and private key.

Diagnostics:

1883:

• Reachable
• Access Token authentication works

8883:

• Test-NetConnection fails
• openssl s_client -connect host:8883 fails with BIO_connect error
• MQTTX reports "Client network socket disconnected before secure TLS connection was established"

Additional checks:

• HTTPS on port 443 works.
• A WebSocket endpoint exists at wss://host/api/ws.
• Port 8084 is not reachable.

My understanding is:

Since TCP connection to 8883 cannot be established, TLS never starts and the client certificate is never presented. Therefore, this seems more like a server endpoint/listener/firewall issue than a certificate issue.

Am I reasoning correctly?

Would you expect an X.509 certificate problem to occur only after a successful TCP connection and TLS handshake?

Based on the diagnostics above, does this point to:

1. MQTT TLS listener not enabled,
2. Firewall/security group blocking 8883,
3. Wrong MQTT TLS endpoint, or something else?

I wanted to know where ThingsBoard deployment works better? Linux with docker or Windows with docker? I'd like to get insights.

I have been working on authentication using certificates. For some just client and ca certificates are enough for verification and others require server certificates too. How does all this work? I wanted to know the importance of root certificates too.

I would love insights.

I've been exploring ThingsBoard and I'm impressed by its architecture and IoT features. However, I'm curious about its scalability in real-world deployments.

What are the practical limits of ThingsBoard CE and PE in terms of:

Number of connected devices

Telemetry ingestion rate (messages/sec)

Data storage capacity

Rule Engine throughput

Horizontal scaling and clustering

Have you used ThingsBoard at scale? What bottlenecks did you encounter, and how did you address them?

I'd appreciate insights from anyone running ThingsBoard in production.

(For context, I'm currently testing ThingsBoard with MQTT, EMQX, Docker, and X.509 authentication, and I'm trying to understand how far ThingsBoard can scale before additional architecture changes become necessary.)