Remote control
for connected devices.

Connecting software to physical devices.

I worked on an IoT control system that connected application-level software with physical devices through MQTT and AWS IoT Core.

The integration enabled real-time remote device management as part of the wider product experience.

Software doesn't stop at the API boundary.

Connected hardware uses a different communication model from a conventional request-response application. Commands need to move between software and devices operating remotely.

For this project, MQTT and AWS IoT Core provided the communication layer for real-time device control.

Event-driven communication between product and device.

I integrated MQTT-based device communication through AWS IoT Core, connecting application logic with remote device control and making device operations part of the product's backend workflow.

This conceptual flow explains the integration; it is not a complete infrastructure diagram.

1. Product / application

   • Remote device operations

2. Backend

   • Application logic

3. MQTT

   • Device-control messaging

4. AWS IoT Core

   • Connected-device communication

5. Connected device

   • Remote control

My contribution.

MQTT integration

Integrated MQTT-based communication for remote device control.

AWS IoT Core

Connected the application's device-control flow through AWS IoT Core.

Product integration

Worked across the software layer needed to make remote device operations part of the wider product experience.

When the backend reaches into the physical world.

The software communicates beyond browsers, mobile apps and other services: its actions ultimately affect physical devices operating remotely.

MQTT provided the messaging model, while AWS IoT Core connected that communication to the application's device-control flow.

Remote control, in real time.

The integration enabled connected devices to be managed remotely through the product using MQTT-based communication and AWS IoT Core.

• MQTT
• AWS IoT Core
• Node.js