Jonathon Feldman wrote in February “Why IaaS Won’t Happen in Most Enterprises“. He makes the argument that departmental business needs will drive spending on Platform as a Service provisioning. The argument is a solid one that Konduit has been using to satisfy end-user needs for over ten years.
Like software application development tool vendors, most PaaS providers rely upon a following of freelance web programmers to train and certify in their technology, all at significant time and dollar investment. If they attract enough followers, then major tool vendors eye them for acquisition, which is followed by migration or deprecation, leaving customers to start over again.
When PaaS licensing is combined with application development services so that customers are not left with unsupported mash ups, we call that Support. The development, deployment, and support of applications written using Konduit’s Transaction Editor Platform as a Service stays within the control of Konduit engineers. A customer’s subject matter experts remain in control of the work flow and practices that define the software’s functionality, without having to understand the mechanics underlying the computer logic, security, reliability, or presentation methodologies. They just get to use it and share it as needed. In essence, Support as a Service, provides infrastructure, platform, and services to the end-user without requiring their understanding of the technology. Unfortunately the acronym SaaS has already been taken. Please comment with your ideas for a new acronym for Support as a Service.