BongoMaker

wasted 2 hours on Tx and Rx

4 bar load sheeding er por ei obdi hoye uthe aslo🙂🙂

Tiny cute Dinosaurs

What do you think? Will it work? Testing its limit....

While building my IoT platform, I initially designed the database specifically for my AC dimmer. It worked well for one product, but I quickly realized it would become difficult to support future devices like smart switches, plugs, or sensors without major database changes.

That experience led me to redesign the database with scalability in mind.

Here are the key principles I now follow:

* Design for multiple device types, not just one product.
* Keep users, devices, and telemetry in separate tables.
* Give every device a unique Device ID/Serial Number.
* Store firmware versions separately to support OTA updates.
* Separate current device state from historical telemetry.
* Log important events for debugging and auditing.
* Build a flexible schema so new devices can be added without redesigning the database.
* Use proper relationships and indexing for better performance.
* Keep business logic in the application layer, not in the database.
* Design for an IoT ecosystem, not just a single device.

Lesson learned: A scalable IoT platform starts with a scalable database. Thinking ahead early can save countless hours of refactoring as your platform grows.