Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
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
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
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
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Joe McKendrick's recent post comments that many analysts are now putting SOA governance and SOA management tools into a single category. He cites arguments that they are in fact very different, stating that while governance is about managing the development and the life cycle of services, management is about the technical monitoring of such. I couldn’t agree more.
Lets spell it out: in simple terms SOA governance is focused mainly on the development process, while SOA management is focused on the 'running' aspects of SOA infrastructure. Management systems must ensure that that the business services in the SOA remain reliable and live up to the expectations of the business partners, customers, suppliers, internal users and regulators.
I believe people are confused by the various contexts in which the term "SOA governance is used." In the context of a product category it is indeed confusing to lump together products with very different uses and characteristics. However, if an organisation is designing a "SOA governance strategy" then tools to aid in the development life cycle of services as well as tools to allow those services to be monitored at run-time may be required. Some organisations may describe this latter capability as "runtime governance."
Developmental governance and run-time management tools are distinct but closely related. They both aid to make SOA successful. Increasingly they work together to form a link across the entire life cycle of development and production deployment, in terms of enforcing and sharing enterprise and business policy.
So, feel free to think about the governance of your SOA in holistic, wide-ranging terms. But when it comes to thinking about which products to use, remember the distinctions. The fog of confusion will only arise if you don't.
View all posts from Giles Nelson on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 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.