1 Answer
- Newest
- Most votes
- Most comments
0
Hi. Per the READMEs (and as David just mentioned in his comment), the V2 SDKs are:
built on the AWS Common Runtime, a collection of libraries written in C to be cross-platform, high-performance, secure, and reliable.
The CPP, Python, Java and JS V2 SDKs all use the awscrt and all benefit from the reuse of common code. Since the V2 SDKs have been around for a long time already, and the V1 SDKs only get security updates, the V1 SDKs lack many of the more recent AWS IoT features compared to V2. For example (depending on the language), named shadows, Greengrass IPC, PCKS11, fleet provisioning, device defender and more.
Additionally, all of the V2 SDKs are validated against AWS IoT Core Device Advisor.
Relevant content
- asked 9 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
Which SDK are you using? Regarding your questions for rollouts or cross testing with v2 and v1, both v2 and v1 continue to use the standard AWS IoT MQTT, Websocket, and HTTP endpoints and commands; i.e. pub/sub to MQTT topics, or Shadow endpoints remain the same regardless of which version you are using.
As stated in the README for the Javascript SDK (https://github.com/aws/aws-iot-device-sdk-js-v2):
This SDK is built on the AWS Common Runtime, a collection of libraries (aws-c-common, aws-c-io, aws-c-mqtt, aws-c-http, aws-c-cal ...) written in C to be cross-platform, high-performance, secure, and reliable. The libraries are bound to JS by the awscrt package.
Each of the V2 IoT SDKs have been developed to use the AWS Common Runtime with the same goals in mind.
Thanks David We are already using using IOT java v1 SDK. while doing load testing we encountered AWSIotException: too many publishes. One possible reason could be maxInflightMessage count which is 10 by default and can't be changed in v1 SDK. So can it be resolved in v2 sdk. Also we get disconnect after every 24hrs from Mqtt Client and we need to refresh credentials for that. Is the new version using same methods?