AWS IOT SDK v2 migration from v1 #301
-
|
We need to know why we are migrating from v1 sdk to v2.? What are the major issues in v1 sdk and how is it impacting our clients.? What are major advantages of IOT v2 sdk. and how many clients it will benefit.? what should be the rollout plan for v2 sdk changes. Can we cross v2 API with some v1 API and then test it. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
The main purpose of the v2 sdks was to use the common runtime (crt) so that the experience across multiple platforms/languages would be the same. There are many reasons why you might want to migrate, but it would depend on your use case. Can you be more specific about your questions about this sdk? |
Beta Was this translation helpful? Give feedback.
-
|
We are documenting the reasons for the benefits of v2 sdk over v1 sdk and some pain points in v1 sdk. Can you please elaborate on some major benefits of v2 sdk and how many clients can be benefitted by that. We were using java v1 IOT sdk for our current services. We are using blocking API to publish messages and maxInflightMessage count as 10 (default). |
Beta Was this translation helpful? Give feedback.
-
|
The sdk does not limit the messages that you are sending rather IoT core sets these limits. You can find those here, and some of them can be increased by request. Requesting a quota increase can be done via the links on that page. With the v2 sdk you can use certificates that can be valid for any length of time. The sdk will manage your connection for you and will reconnect if you temporarily lose connection (as long as the certs are still valid). |
Beta Was this translation helpful? Give feedback.
-
|
The v2 SDK implements the standard default credentials provider chain you are used to from the standard AWS SDKs (with the exception of one or two of the most recent providers like SSO). Reconnection will automatically refresh credentials as necessary based on expiration time; there is no need to manually disconnect. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
The v2 SDK implements the standard default credentials provider chain you are used to from the standard AWS SDKs (with the exception of one or two of the most recent providers like SSO). Reconnection will automatically refresh credentials as necessary based on expiration time; there is no need to manually disconnect.