Comprehensive solution for crafting and managing sophisticated digital experiences
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
Lately there has been a lot of buzz -- more than just buzz, really. The topic has been Node.js. And when companies as well known as Uber, Walmart, Groupon, and PayPal have been putting many of their “eggs” in this new basket called Node.js, it’s time to pay attention.
How does this work? Web-serving techniques have traditionally required that each connection create a new thread. This process takes up system RAM and eventually gobbles up remaining resources. By contrast, Node.js can act as a single-thread, using non-blocking I/O calls, so that it can handle thousands of concurrent connections, without running up against RAM limitations or the complexity of context-switching between threads.
The single-thread approach makes Node.js ideal for highly concurrent applications. It also makes development easier because developers don't have to worry about handling multiple threads in their application. Node.js takes an event-driven focus on the server-side and pushes data to clients only when appropriate, making it hugely scalable!
Naturally, Progress sees Node.js as a powerful option for existing and future customers – the people that are experts at delivering rich and rugged functionality to enterprises around the globe. And that thinking has driven an important business decision for us. Modulus, the Node.js PaaS vendor that Progress has just acquired, is already a trusted name for members of the Node.js community – and its enterprise-oriented technologies make it an ideal entry point for other experienced developers interested in leveraging Node.js.
At Progress, where we have always focused on helping IT professionals move ahead – to do more and be more productive – we see Modulus and Node.js as complementary to many of the things we already do and already provide. In particular, Modulus is a natural fit with Progress Pacific and Progress OpenEdge. It will enable us to expand Pacific to become both a productivity and a control platform. In short, Modulus provides a fresh way to address application challenges – one that can be helpful for any organization that needs to do more and more with less and less...
On a more personal level, having spent much of my career working in open communities (Java, J2EE, Glassfish, Red Hat, MySQL, PostgreSQL), I am very happy to have Progress make investments in the Node.js community. Open source is not just about free software, but is a mechanism by which the smartest people across the planet can collaborate and innovate and that is clearly demonstrated in the growing Node.js community.
Karen Tegan Padir is the president of the Application Development and Deployment Business Unit at Progress, reporting to President and Chief Executive Officer Phil Pead. Padir, a 20-year software industry veteran, is responsible for the strategy and growth of Progress application development assets including Telerik, Modulus, Rollbase and the Pacific Platform.
Copyright © 2016, 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 or appropriate markings.