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
The Progress® OpenEdge® community has many frameworks for modernizing OpenEdge business applications. Some of these frameworks–such as ADM1 and ADM2–were created by Progress. Others were created by the OpenEdge community.
When done right, frameworks help improve productivity by providing common functionality such as security, configuration, session management and more. But many times, our partners and customers feel locked in by a framework—as if it is an all-or-nothing proposition.
There are many communities that have come together as a group to successfully create standard specifications–such as Java or W3C. In such instances, a group of companies create a standard specification, then implement multiple iterations of that specification. For example, JMS specification was created by Java Community and implemented by vendors such as Sonic and ActiveMQ.
Wouldn't it be great to have common business application components that could interoperate because they work on community-driven standards? Standardizing common components of business applications would greatly help the entire OpenEdge community to more quickly, easily and cost-effectively modernize applications, and take advantage of the latest features for those components.
That’s why we launched the CCS Project–to create standard specifications driven by the OpenEdge community, openly and transparently.
A specification with interfaces, dependencies and compliance criteria will help create a structure that enables interoperability. It also enables the creation of tools based on a standard that can be leveraged across different implementations.
You might be thinking, “We don’t use a framework, so none of this applies to me.” Not so. Framework or not, every business application needs common components. If you don’t use a framework, it means you had to write those components yourself.
Here’s what it means for your business: by helping to develop standard specifications, you can influence the direction of those specifications. And, by aligning your implementation with the standard specification, you can take advantage of the standard tools built for those components.
Many of us have been writing business applications for a long time. We have the expertise. Now it’s time for us to come together as an OpenEdge community and build something that defines the future of business applications. That’s powerful!
Let’s get started. Apply to participate in the Common Components Specifications Project!
Sunil Belgaonkar brings more than 22 years of software industry experience to his position at Progress, and is currently responsible for the strategy and direction of OpenEdge business.
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 or appropriate markings.