Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile 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
A complete cloud platform for an app or your entire digital business
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-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
The "need for speed" is a misconception that has driven software development for too long. I have a ’66 GTO with more speed than I know what to do with. I wondered what features, other than speed, would get me to upgrade?
I have worked at Progress as a software engineer for more than 20 years and this is my first blog post. Why did I decide to write a blog post now? Well, I have been struggling with a misconception that has driven software for many years, which is that the only reason to upgrade to or even develop new software is for faster performance.
I recently slammed head-on into this “need for speed” mindset while working to develop our new WebSpeed feature in the recently released Progress Pacific Application Server for OpenEdge (hereafter to be called: PASOE).
Now, in our previous release of PASOE, we upgraded our classic AppServer architecture. As a result, PASOE was expected to have better performance and use fewer resources than our classic AppServer as a core part of its designed features.
In PASOE 11.6 we have added WebSpeed functionality, and we’re very excited about how it improves the product. However, WebSpeed has always been very fast, so pure performance was not high on the required features. This is where the “need for speed” mindset ambushed us. We were confronted with the requirement of demonstrably “faster” performance because of the feeling that it is what customers will expect.
While struggling with this requirement, I knew there were several reasons other than speed for upgrading to the new WebSpeed. At first, I was at a loss for how to explain it, but then I got to thinking about a hobby of mine.
That hobby is classic muscle cars. I have a ’66 GTO (hereafter to be known as: Bernadette) with more speed than I know what to do with. I wondered what features, other than speed, would get me to upgrade Bernadette?
There’s no doubt that any of these improvements would be a nice upgrade, even if the top speed only remained level. Now that we have a shopping list of improvements for Bernadette, how does that relate back to WebSpeed?
We’re very proud of our new product and its features, but not just because it’s faster! There are many great improvements added even beyond the new WebSpeed too. Please download the new 11.6 OpenEdge and see if you like our new muscle car!
Roy has worked at Progress for over 20 years. After starting in Technical Support, Roy moved to the WebSpeed development team. Since then he has helped to deliver many products and features, including: the AdminServer, NameServer, AppServer, OpenEdge Explorer and Management, Arcade and recently the new Progress Application Server for OpenEdge. He enjoys working with customers and presenting at many customer events.
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.