Software as a Web Service
From Wikipedia, the free encyclopedia
 |
This article may require cleanup to meet Wikipedia's quality standards. Please discuss this issue on the talk page or replace this tag with a more specific message. This article has been tagged since December 2006. |
Software as a Web Service, SaaWS, is an emerging demand from Fortune 1000 companies. It is very similar to Software as a Service, except that there is no real need for a user experience or user interface. This has many implications for the software industry.
Contents |
[edit] Assertion
A new breed of software vendors has emerged and will continue to emerge in a grand fashion, based on current trends.
[edit] Implications
The next wave of enterprise applications my cost significant less, may simply be hosted application engine mash ups, SAP and Oracle may fundamentally undo large revenue streams by surrounding their applications with SOA.
The true world of mash ups has just begun, with a fizzle, not a bang. The coming bang will occur when pragmatic SOA demands, that more and more software companies offer their applications with a complete SOA surround and the ability to completely decouple the user interface. While this might not seem like a "bang", this article hopes to demonstrate some potential powerful shifts for enterprise applications, in addition to consumer web applications. To iterate this statement another way, this is NOT a simplistic mash up, like now being seen on the web, for example maps with retailers, time and temperature. But rather, applications that take the total cost of ownership of, for example an enterprise payroll system, down by a magnitude of ten.
[edit] Pragmatic SOA
A pragmatic Service Oriented Architecture can now exist for most companies who started down the path to SOA, two or more years ago. On the journey to pragmatic SOA, many will notice that if a software offering were architected in the beginning of its life cycle, with an intent or possibility to completely decouple the user interface, that it is possible to now mash up or utilize this offering as purely an "application engine" and create a "greater than the parts" whole by assembling the combined application functionality to into seemingly one application.
[edit] References
Clear Channel Information Technology, Enterprise Architectural group, led by John Szurek, Justin Myrick, and David Jemeyson Microsoft, Architectural Team, Mark Baciak SourceCode, K2.Net product team and Executive Management, Hennie Lauschbaucher
Accenture, "Enterprise Applications: The coming wave of change"
Pragmatic Service Oriented Architecture. (2006, December 16). In Wikipedia, The Free Encyclopedia. Retrieved 16:21, December 16, 2006, from http://en.wikipedia.org/w/index.php?title=Pragmatic_Service_Oriented_Architecture&oldid=94717731
