{"repo":"aws-greengrass/aws-greengrass-nucleus","free":true,"listed":false,"github":"https://github.com/aws-greengrass/aws-greengrass-nucleus","clone":"git clone https://github.com/aws-greengrass/aws-greengrass-nucleus.git","description":"The Greengrass nucleus component provides functionality for device side orchestration of deployments and lifecycle management for execution of Greengrass components and applications. This includes features such as starting, stopping, and monitoring execution of components and apps, interprocess communication server for communication between components, component installation and configuration management.","language":"Java","stars":118,"topics":["aws","java","greengrass","iot","edge-computing"],"license":"Apache-2.0","category":"workflow-automation","readme_excerpt":"Greengrass Nucleus Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0 The Greengrass nucleus component provides functionality for device side orchestration of deployments and lifecycle management for execution of Greengrass components and applications. This includes features such as starting, stopping, and monitoring execution of components and apps, interprocess communication server for communication between components, component installation and configuration management. It manages the model that describes the software running on the device. The model is a dependency graph of services . Services have three primary aspects: - Configuration - Dependencies on other services - A set of lifecycle phases in the form of a finite state machine. A service may have processes, threads, code, network connections, ... But not necessarily. Some have all of these, some have only one. You can think of the nucleus as a mash-up of make , a super-lightweight publish/subscribe system, and a small hierarchic key-value data store. The various services have continuously varying states that the nucleus monitors and manages. A dependent service is not started until its dependencies are started, and if they become unstable, the dependent service is notified. The internal interconnections are handled via dependency injection. Restarts are managed automatically. When configuration changes, all users of them are notified. Everything adapts continuousl","default_branch":null,"files":null,"tree":[],"storefront":"/r/aws-greengrass","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/aws-greengrass/aws-greengrass-nucleus/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}