1 Answer
- Newest
- Most votes
- Most comments
1
- Pubsub is part of Nucleus. The documentation always tells you what requirements there are, if any: https://docs.aws.amazon.com/greengrass/v2/developerguide/ipc-publish-subscribe.html. MQTT bridge component is only useful when you have client devices connecting to a local Greengrass broker.
- Pubsub is implemented on top of eventstreams in C, you can see the implementation is opensource: https://github.com/aws/aws-iot-device-sdk-java-v2. If you are running out of memory then something is pretty wrong. Did you configure Greengrass Nucleus with a maximum java heap size? 8MB is generally very large for messages, it can certainly work if you have enough memory free on the device and allocated to Greengrass's Java, but I'd recommend you do not do bulk data transfer using pubsub. You may instead use pubsub to communicate enough information to then setup a high speed direct transfer mechanism between your components. eg: gRPC, memory mapped files, etc.
- Greengrass IPC communication requires authentication and authorization, no external component can connect to Greengrass. The Greengrass local CLI supports publishing and subscribing and the Local Debug Console also supports this.
Relevant content
- asked 2 years ago
- asked 8 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 12 days ago
Thanks so much for the quick response and links!