Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Chris Longo gives three reasons why Node.js is better than shell script for working with BI data.
It can be tempting to wait a bit too long to adopt technologies that are new for the sake of the tech we trust. Node.js might seem like one of those sit and wait cases. Yet at Progress® BravePoint®, we are using Node.js with Progress® OpenEdge® today in professional services engagements.
At BravePoint, we are using Node.js in client engagements to access and update critical business intelligence data. From a developer perspective, Node.js has three clear advantages over shell scripting:
A BravePoint Node.js use case
One example of our use of Node.js at BravePoint is as a data transfer broadcast hub. Push notifications of certain application events and triggers are sent to their subscribers. With Node.js, such data can be pushed in real time to GUI clients or browser subscribers.
Chris Longo is a Professional Services Manager for Progress BravePoint in Atlanta, GA. An experienced Progress OpenEdge application developer since 1985, Chris has designed and delivered OpenEdge training at numerous Progress events, including Progress User Group sessions and Progress Exchange.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.