Friday, February 13, 2009

Windows Azure with David Chappell at Bay.NET

David Chappell, Distingished Speaker spoke (1/28) @ Bay.NET User Group. Foot Hills Technical College, Los Altos, CA.

* Backgrounder
* Azure Services Platform by David Chappell
* Future Direction
* Impact
* Steps to move Apps into AZURE...




Backgrounder

AZURE is Microsoft's platform entry into Cloud Computing. The name means encompasses; Windows Azure vs Azure (the whole platform) vs Azure Platform Services. More http://www.microsoft.com/azure/default.mspx , http://en.wikipedia.org/wiki/Azure_Services_Platform

Azure Services Platform by David Chappell

David PPT slides covered Overview, Architecture, Characteristics

Architecture

* VM's are Win 2008 64-bit
* Web Apps supported, any which can invoke IIS7
* Data Access is RESTful (ADO.NET apps not supported)
* Azure service model has an config file - (yay, config)
* SQL Server not supported, all data storage is Tables.
* Tables are supported like schema free. Allowing horizontal sharding over multiple data servers ("MSFT must have hired an architect from Google, or Grid company)

Future Direction

Currently Azure does not host SQL server instances. The current data structure is tables accessed via RESTful services. David Chappell polled the audience of about 100, what they needed (I know many are CTO, Architects or Lead Developers working on business apps). Perhaps predictably out of familiarity, people wanted SQL services (this was not a Google audience). David mentioned he is in Redmond next week meeting the head of Azure, after touring Europe, Brussels, Amsterdam and meeting with big banks and groups like Bay.NET and not to be surprised if Microsoft switches to supporting SQL server, just like Amazon EC2 does (its paid option over the standard SimpleDB). Azure does have access to on premise SQL server data via a service bus....


Impact

* "Some data will never go in the cloud, which goes where is the issue" - David Chappell.
* Data written to Azure storage is saved to 3 physically different data stores.
* Financial data vs CRM - Compliance / Trust. On premise Accounting (Compliance) vs Saas (Trust).
* Apparently Sarbanes Oxley does not allow Financial Data off premise, yet CRM data is allowed off premise, SalesForce.com - David Chappell. (I plan to research Sarbanes, true or not)
* Cloud Computing is heaven for start-ups, 2 guys can lever the Cloud Platform and look like 200.
* 250 guys can look like 2500. No VC funding needed, just a credit card an go
* Integration to other web sites services, like Sales Force.CRM or Google maps is potentially far easier in the Cloud, but may be more expensive depending on how data is metered.

Steps to move Apps into AZURE…

The big conceptual change for developers / CTOs / founders / etc where do you want store the data, at customer premises, like most Client Server Apps. In data center like your ATM account is hosted by a bank, hosted under the lock and key of our your IT team, or hosted in Microsoft data centers around the world. What data goes where, financial on premise, CRM data in Azure, HR data on premise. All of a sudden more questions, without obvious answers.

Final thoughts, many codecamps required before moving forward.

Wednesday, February 11, 2009

Debate: Salesforce vs SAP

The Churchill Club hosted a debate between Marc Benioff and Hasso Plattner co-founders of respective companies.


My takeway, contrasts

SAP - high margins, low growth
SF - high growth, low margins

SAP - customisation, change within
SF - configuration, build on top

SAP - slow innovation delivery
SF - fast innovation delivery

SAP - distribution by installation
SF - distribution by browser

SAP - sweet spot, thousands of users
SF - sweet spot, small biz

SAP - IT complexity
SF - IT simplicity

SAP - high pct business functionality coverage
SF - low pct business functionality coverage

SAP - certain privicy
SF - trust privicy

Bottom line, choices

After thought...
SAP - Sales person, BMW and Swiss watch
SF - Sales person, Camry and Swatch watch