[ad_1]
In AWS' Labs repo aws-greengrass-mini-fulfillment, the architecture map seems to fuzzy the line between devices and cores from the simplified descriptions used in the AWS Greengrass page.
In this example, each device (Sorting Host, Master Belt, and Inventory Arm) is its own Greengrass Core with subprocesses as "devices". These Cores, each in their own Groups, then communicate independently to the cloud around a shared MQTT pub/sub thread.
Questions:
- First and foremost, am I reading and understanding this demo architecture correctly?
- Is there an alternative architecture herein that achieves a similar result, while allowing the Sorting Arm and Inventory Arm to communicate only with the Master Host?
[ad_2]
لینک منبع
