Multi-tenant, or just a big single tenant?
That's a good clarification of the announcement, Doug. Marc Benioff is correct when he says a large customer, such as the U.S. government, will have many users. For such a large customer, Salesforce can establish a "pod," which at one time referred to a standard shipping container crammed full of servers, disks and switching gear. It was a pod because it was an independent unit, it had its power supply and you plugged it in and all the servers lit up. Today, Benioff is probably referring to a section of a data center that has its own power supply and secure communications links, or even a location purpose built for a large customer. I can't tell for sure. One place where the integrity of the terminology seems to be slipping is multi-tenant. Yes, the U.S. government has many users and many users will be found on a single SaaS application of a "SuperPod." But the U.S. government per se is a single tenant. If you combined retailers with the U.S. government, then you would have multi-tenants with different use patterns. Retail is extremely active around the holidays when government workers get extended holidays. Multi-tenancy leads to higher overall utliization in the cloud, etc. Salesforce.com's embrace of Oracle seems to have mysteriously lead to a dilution of its former pioneering cloud definitions. What you might be able to defend with multiple agency use by the U.S.government begins to look more like single tenancy when you get to HP and other single tenant, albeit large, users.