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
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
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
Wow, Ron Schmelzer reacted, how should I put it, somewhat unkindly to my last post. Yes Ron, I did read the whole article (and Nick Gall's too!)
I guess my point was probably too subtle. I wasn't reacting to the fact (yes fact) that WOA is a "more concrete" form of SOA (see I did read your article Ron :-). I'm in total agreement with that. My point was, from a naming perspective, that's irrelevant.
Let me use an analogy. Let's say we discovered intelligent carbon-based life on mars. Would it be better to talk about it as "intelligent life" or as "a more specific type of carbon-based organic"? Both are absolutely true, but which one matters more? Obviously "intelligent" is the most important attribute. The fact that it's carbon based is interesting but, in comparison, is not nearly as important (except to a few dedicated biologists who could care less about the practical consequences of it being intelligent).
For me, the same holds true for WOA. What's the most important attribute, that it's "web-oriented" or that it's a "more concrete form of SOA"? The most important attribute is that it's web-oriented. That's where the power of it comes from. The fact that it's a more concrete form of SOA is interesting, but not nearly as important.
That's why I think we should refer to it as WOA, not "web-oriented SOA." We need to put the emPHASis on the right syllABle... Unless you'd prefer that I call you "carbon-based organic Ron" from now on. :-)
View all posts from dan foody on the Progress blog. Connect with us about all things application development and deployment, data integration and digital 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 for appropriate markings.