Hi everyone, I’m setting up an API gateway with Kong to handle incoming data from several ESP32-based IoT sensors and wanted to ask for best practices. For context, I’ve been looking at this ESP32 motion-detection project, where the device sends simple HTTP data: https://www.theengineeringprojects.com/2022/03/iot-based-motion-detection-with-email-alert-using-esp32.html, I’ve also come across a few Arduino and Raspberry Pi forum threads where people push similar sensor updates using basic REST endpoints or MQTT bridges. For those who have integrated IoT data streams with Kong what plugins or patterns have worked well (auth, rate-limiting, retries), and how do you handle lots of small POST requests without introducing extra latency?
Hi, when Kong OSS is considered HTTP/S is the only option. Kong provides great message gateway for such scenarios but it’s part of the enterprise/commercial offering. Nevertheless from my experience with Kong and IoT:
- i would not worry about chattiness nor latency - you did not provide volumetry but handling several sensors streaming data (lets say event every 200ms x 10 sensors gives about 50 req/sec) - this should not be a problem. Eventual lag may be introduced by the upstream service not the Kong gateway itself.
- As per other requirements like auth and traffic limiter - you are safe here with OSS as there are open source plugins for most popular scenarios.
Hope that helps. All the best.