Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Continuous Deployment in IoT Edge devices using Azure
Names and KTH ID
Chandni Rakhashiya ([email protected])
Rohini Bhardwaj ([email protected])
Deadline
Category
Description
In this presentation, we will explain what IoT Edge devices are and highlight the importance of Continuous Deployment (CD) in managing these devices. We'll demonstrate how CD enables automated updates to edge devices, ensuring real-time functionality and scalability. Using Azure IoT Edge as an example, we'll show how to implement CD effectively. Additionally, we'll discuss how CD for IoT Edge differs from traditional web applications, focusing on challenges like connectivity, resource constraints, and decentralized environments.
Relevance
As IoT Edge devices become more prevalent, the need for rapid software updates, bug fixes, security patches, and new feature rollouts across a large, distributed network of devices has grown significantly. This is where Continuous Deployment plays a crucial role. CD allows scalable, secure deployments that minimize downtime and reduce manual intervention.