| AWS Greengrass Now Supports C Executables |
| Written by Kay Ewbank |
| Thursday, 02 August 2018 |
|
An updated version of AWS Greengrass has been released with added support for deploying executables written in C, C++ and in any other language that supports importing of C libraries. AWS Greengrass is designed to let local devices collect and analyze data for use on AWS Cloud. It lets you run local compute, messaging, data caching, sync, and ML inference capabilities for connected devices in a secure way. ML Inference is a feature of AWS Greengrass that lets you perform machine learning inference locally on Greengrass Core devices using models that are built and trained in the cloud.
Developers who use AWS Greengrass can now author serverless code (AWS Lambda functions) in the cloud and deploy it to devices for local execution of applications. Executable code can be invoked by events or invoke other Lambdas, and can take advantage Greengrass features such as Local Resource Access. You can mix and match executable code together with Lambda functions written in interpreted languages such as Python or Node.js. The other changes to Greengrass are designed to make the software handle disconnected devices better. The first improvement for this situation is the ability to change the queue size for locally stored MQTT messages. Greengrass already handles situations where the host device is intermittently disconnected from the Internet by spooling messages intended for publication to the cloud. The updated version lets you configure the queue size to choose the best balance between data retention and conserving local storage space. The other main change for dealing with disconnected devices is the ability to configure the maximum period for which Greengrass attempts to reconnect or retry sending information when the core device is disconnected. When a device is disconnected, the time between attempts to reconnect becomes progressively longer as the attempts fail. The updated version now lets you configure the maximum retry period, so making sure that Greengrass reconnects to the internet quickly once connectivity becomes available. The final improvement to the new version is improved messaging throughput performance.The new update is available to customers at no additional cost in all AWS regions where Greengrass is available.
More InformationRelated ArticlesAmazon Releases Managed Message Broker Service for ActiveMQ AWS Lambda for the Impatient Part 1 AWS Lambda for the Impatient Part 2 AWS Lambda for the Impatient Part 3 Amazon Adds Game Dev Options To AWS Amazon Strengthens Data Offerings New Amazon Elasticsearch Service
To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin. 
Comments
or email your comment to: comments@i-programmer.info |
| Last Updated ( Thursday, 02 August 2018 ) |
