Comments

Congrats to all involved with Rx, a living proof project of the power of mathematics, theoretical computer science and practical software engineering used to simplify and advance software development!

Great talk about the middleware challenges and how Microsoft addresses them. Minutes of interest:

10:40 Microsoft middleware programming model

12:40 solutions for the islands of capability

17:30 Appfabric container

22:27 Appfabric cache

23:10 Service bus

26:10 Azure demo

Most Interesting points @ minutes: 29:06, 35:20, 42:00, 46:40, 51:10, 53:50, 57:50, 1:02:53

27:20 Cloud challenge nr 1: Scale
  lots of users, data, always busy: how to think different about scalability
    Scale up is not the solution. Scale out is.
29:06 a. Scale the services: First scale out option:
        partition the app in:
          as set of async loosely coupled services
     31:15 example of message coupled sell & inventory services

35:20 The message based design pattern allows possible release of part of the software. Cloud changes the way we think about software.

36:20 b. scale data. SQL Azure Federations supports "sharding" cloud scale data

partioned across multiple physical tables
  partition diff tables by region
    very hard problem

39:30 c. State maintanance in scale scenario
 big challenge to keep cloud elastic + solutions (minimize & isolate state in the service)
 AppFabric cache services to the rescue

42:00 Performance becomes explicit in the cloud
  because of charging model for cloud usage (storage, round-trips, etc.)

46:40 cost of operation affects sys design
   cost of SQL Azure storage is higher than windows blob storage

47:10 service success is determined by its manageability
 "One Microsoft" cloud experience with different MS enterprise products

50:20 provide service visibility to the customer (up-time, scheduled events, etc.)

51:10 Cloud error reporting and propagation adds new complexity
 need for platform services & APIs for error reporting

52:40 cost effective manageability of service

53:50 new reality: combination of cloud &
                private devices (on-premises due to regulatory, merging, etc.)

55:30 Identity

56:10 Equivalent of liveID in the enterprise envir (online ID, bussiness equivalent available in the cloud, similar to AD)

57:50 connect scenarios from cloud to premises
   azure service bus, CRM eventing model

58:25 Customization for Cloud Systems
 declarative model-driven customization

1:02:53 Other Cloud Considerations
   focus on simplicity
       should be rich but easy to startup, customize & upgrade
       remove features

   Privacy & data security
     raised to new levels

   Component failure
      assume failure due to huge nr of nodes
      recover state info in case of failure

1:09:30 on-premises customers benefit from cloud investment

1:11:23 The cloud enables new scenarios
 shared data
   payroll regulation
 connections
  connected big supply chains
    limit number of interfaces if everyone talks with a cloud hub
 new analytics, reveals otherwise invisible trends
  across massive data in the cloud
    example: determine flu trends via queries
  
1:18:10 Q&A

1:22:38 how MS deals with competitors?

Great talk about how cloud computing changes software development requiring a "think different" paradigm.

Nice explanation of the differences between traditional application package, IaaS (Infrastructure as a Service), PaaS (Platform as a Service) and SaaS (Software as a Service) covering what part of the application stack is dealt by the vendors.

Nice explanation of cloud computing advantages compared with traditional regarding IT capacity demand and supply.

Up to min 3:00: How traditional IT addresses the increased capacity demand.

From min 3:00: How cloud computing supply on demand smoothens the IT capacity demand & supply equation.

Watch Doug Crockford's last year MIX10 tale on Javascript (http://channel9.msdn.com/Events/MIX/MIX10/EX39) for an amazing and intriguing story of the controversial, intriguing and popular language.

A language designed only in 10 days takes the world by storm in a unique way in spite of the initial design bugs. A COBOL vs Javascript language design and evolution process comparison would be interesting

Interesting bookmarks from the last year tale:
min 7:21 the language has been designed in 10 days
min 14:51 Funny year 2000 prediction on the end of the web after Netscape's failure
min 18:15 Javascript becomes the most popular language
min 18:40 also most unpopular language
Good parts explained till minute 35:37
What's next for Javascript from minute 35:37.

Who said computer science and technologies tales are not entertaining?

Who says computer science and technologies tales are not entertaining?

A language designed only in 10 days takes the world by storm in a unique way in spite of the initial design bugs.

Interesting bookmarks:
min 7:21 the language has been designed in 10 days
min 14:51 funny year 2000 prediction of the end of the web after Netscape's failure
min 18:15 Javascript becomes the most popular language
min 18:40 also most unpopular language
Good parts explained till minute 35:37
What's next for Javascript from minute 35:37.

A great talk indeeed!

great points at minutes:
4:34 need for agility rules: set a context where people are motivated
9:30 safe fail emnvironment must be factored in
14:50 code monkey mentality
16:30 programmer as trusted advisor
17:10 focus on value

Cloud Computing is OSSM read as awesome
Cloud computing in 4 characters is OSSM
O = on-demand = service is setup & ready for u
S = self-service = u turn it on or off when u want
S = scallable = get more resources as you need
M = measurable = u get what u pay for