Azure IoT edge uses container based modules, while AWS greengrass is process centric. It will be interesting to understand the trade-offs, and how might the two evolve in the future? Would like to hear your opinion.
Asked
Active
Viewed 809 times
1
-
1There are some [benefits](https://www.docker.com/docker-azure#/features). – Rita Han Feb 21 '18 at 05:23
1 Answers
1
With Greengrass already out in the market, Azure had the advantage of hindsight in launching their Edge intelligence and IoT Edge.
- With Container approach, customers are able to use their existing containerized applications. This seems to be an interesting approach - vs requiring customers to build Lambda function - for those apps to run on Lambda runtime in case of AWS. Azure IoT Edge runtime allows you to run these containerized application out of the box.
- Azure IoT Edge Modules are Portable (because of container approach) vs AWS Lambda functions.
- As of this writing there are Lambda resource limits such as the size of your deployment package or the amount of memory your Lambda function is allocated per invocation. I am sure AWS will change this in the future. There is no such limitation when you run containerized applications. (Of course Docker Containers have their own limitations on security which can be overcome).
Vamsi Sistla
- 136
- 5
-
In Greengrass you can run long lasting Lambda functions, which is not subject to time limitations and can run indefinitely. – Halim Qarroum Apr 14 '18 at 15:26
-
My bad - I meant to say Lambda resource limits such as the size of your deployment package or the amount of memory your Lambda function is allocated per invocation. I will edit my response. Thanks. – Vamsi Sistla Apr 14 '18 at 22:13