Usage recommendation between aws-iot-device-sdk-cpp-v2 and aws-iot-device-client

[tiny-dancer]

Hey all,

We are beginning our aws iot journey and looking to reconcile how aws-iot-device-sdk-cpp-v2 and aws-iot-device-client relate to each other.

• What use cases would lead someone to choose one over the other?
• Is aws-iot-device-sdk-cpp-v2 seen as the successor to aws-iot-device-client?
• Is one more aligned for resource constrained devices?

Thanks

Feel free to point towards any existing documentation on the topic

[jmklix]

aws-iot-device-sdk-cpp-v2 is the successor to aws-iot-device-sdk-cpp. The v2 sdk uses CRT dependencies (common runtime) for better performance and uniformity across languages. aws-iot-device-sdk-cpp-v2 is intended to be used with common operating systems; Windows, Mac, Linux(ubuntu). While aws-iot-device-client is designed for use on Embedded Linux devices. You probably want to use aws-iot-device-sdk-cpp-v2 unless have a specific reason to use embedded linux.

Embedded Linux vs Desktop Linux:

Linux operating system is used in desktop, servers and in embedded system also. In embedded system it is used as Real Time Operating System. There are so many products in the market that use embedded linux. Embedded system requirements are very much different then requirements of desktop system. Desktop PCs are mostly designed around 8086 architecture of microprocessors. But embedded system products can be designed on various of microprocessor architectures like Power, ColdFire, ARM, 8051, PIC, AVR etc. In embedded system memory is limited, hard disk is not present, display screen is small etc.

[tiny-dancer]

aws-iot-device-sdk-cpp-v2 is intended to be used with common operating systems; Windows, Mac, Linux(ubuntu). While aws-iot-device-client is designed for use on Embedded Linux devices.

@jmklix thank you this nails it home. We are operating in an embedded environment with a custom linux distro via yocto and are using https://github.com/aws4embeddedlinux/meta-aws.

I am curious, it appears the device client is built on top of the sdk, what leads to the device client being designed for embedded if the sdk it consumes is intended for common operating systems?

[jmklix]

Device client is for Linux based systems - ranging from general purpose embedded systems to fit for purpose embedded systems

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.