-
Notifications
You must be signed in to change notification settings - Fork 428
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Presentation proposal for week 3 (#2441)
* Presentation proposal for week 3 * Updated README.md
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Assignment Proposal | ||
## Title | ||
Continuous Deployment in IoT Edge devices using Azure | ||
|
||
## Names and KTH ID | ||
- Chandni Rakhashiya ([email protected]) | ||
- Rohini Bhardwaj ([email protected]) | ||
## Deadline | ||
- Week 3 | ||
## Category | ||
- Presentation | ||
## 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. |