Now, Peter Coffee from salesforce.com is up. He believes that “Enterprise cloud computing implies API leverage”. Start conversation with the function you want to perform, not the underlying technology.
He has a quote up from William S. McNee, of Saugatuck Technology “On-premise computing is going to drop-off a cliff” (or something close to that, the slide changed)
Salesforce cloud began with CRM… Fundamental ideas: enterprise software accessible via web, web-based systems should be designed for global scale, everything not distinct to customer should be shared, everything distinct to customer should be customizable
|user interface as a service|
|logic as a service|
|integration as a service|
|database as a service|
|infrastructure as a service|
Ok,Peter talks way too fast… plugged Python as something IBM Rexx programmers would like.
Enterprise wants secure, high available, low cost solutions. Enterprise is not, anti-cloud. If these characteristics exist, enterprise will move to cloud. If it’s too difficult to move existing portfolio to cloud, then keep that in-house and go forward on cloud.
many tech trends oppose governance goals:
– processing availability is enemy of encryption
– connectivity provides attacker opportunities and tools
– storage, ever growing risk of larger data losses (thumb drives, laptops, email)
Service models offer greater leverage:
– granular management of roles & privileges
– data is in the cloud, not carried around and subject to physical loss
– [one more, sorry…]
Now, talking of developer productivity using force.com vs. java development; overall project cost 30-40% less
Points to charts and metrics from the economics of the cloud post on O’Reilly.
PaaS puts IT spending back in balance. Conventional IT model front-loads capital expenditure on infrastructure. PaaS enables preparation for upturn. Build now without big up-front investment, scale at upturn via PaaS.
“Do not mistake the consumer Web for the enterprise cloud”. It’s not like putting your G/L on facebook.