A leading cloud analyst recently told me that there are exactly two ways to
operate software: Software-as-a-Service (SaaS) and on-premises. He said,
"Either they run in the cloud and someone else takes full responsibility for
the underlying physical infrastructure and system management (SaaS); or they
run on your own equipment and you operate it yourself (on-prem)."
I said, "Not so fast."
To be sure, there are models where some of the administration is outsourced,
such as shared hosting or managed services. But these approaches still leave
the financial and management burden with the customer, so they are merely
variants of on-premises application deployment.
The public Infrastructure-as-a-Service (IaaS) model blurs the distinction
between SaaS and on-premises. With IaaS, a company can remove itself
completely from the financial and management aspects of operating t... (more)
Think back to when you were a kid. Remember that thing you thought, felt,
wanted or did that you were embarrassed about? You probably worried that you
were the only person in the world who had that thought, feeling, desire or
behavior. It was your Little Secret. Only as you got older did you figure out
that it was actually pretty common, that everyone did that, or felt that way,
at least once in a while. And that maybe it even had a name.
If you're a nerd like me, you probably had more than one of these.
As we've talked to customers, prospects and vendors in the industry, we've
Like an automobile, a web application needs occasional maintenance and
management over its life cycle. Although it doesn't need oil changes, it will
probably need version upgrades. There may not be manufacturer recalls, but
sometimes servers fail or hang. An application doesn't need to be washed and
detailed, but it does need to be backed up. And both cars and applications
need occasional performance tuning.
This article provides a complete list of the system management functions that
need to be performed on a standard architecture web application, with a
particular emphasis on ... (more)
In an application deployed directly on IaaS, you know and control everything
about the database; in a SaaS application you know little and control
But how does it work in PaaS?
Since a PaaS is essentially a container that runs application code, and
virtually every application requires a persistent data store, most PaaS
offerings provide some kind of database services. Not surprisingly, Resource
PaaS offerings most closely resemble SaaS in that they hide more deployment
details, while Server PaaS offerings are more flexible but potentially more
complex. (For more on Res... (more)
Despite my shaky prediction performance in 2011, I'm going to try again.
Last year, my best predictions were based on some sort of specialized
knowledge or insight, and the worst came from looking into the macro
environment and making guesses. So, this year's predictions emphasize the
former approach, yet hopefully avoid sounding like claims such as "the market
1. 2012 will be the Year of the Storefront in the cloud.
Admittedly, this is a somewhat self-serving prediction, since Standing Cloud
is (among other things) a storefront. But based on the variety of offerin... (more)