1. Visual Studio 2010 and.NET Framework 4 Training Workshop

2. Presentation Outline (hidden slide): Technical Level: 300 Intended Audience: Developers & Architects Objectives (what do you want the audience to take away): Understand why Velocity is being introduced Understand how to use Velocity Presentation Outline: Data Types “Velocity”: What/Why/Where? Concepts Features Futures

3. A Lap Around “Velocity” Name Title Organization Email

4. Agenda Data Types “Velocity”: What/Why/Where? Concepts Features Futures

5. What kind of data do we work with in our applications?

6. Data Types Reference Read* Mostly static High traffic High Availability Application-wide Reference Read* Mostly static High traffic High Availability Application-wide Activity Read/Write Changes heavily User-specific High-Scale Activity Read/Write Changes heavily User-specific High-Scale Resource Read/Write Changes heavily Application-Wide High-Scale Resource Read/Write Changes heavily Application-Wide High-Scale Examples: 1)States 2)Catalog Examples: 1)Session 2)Shopping Cart Examples: 1)Inventory

7. Alright great, so how does “Velocity” help, if at all?

8. What? Unified Cache View An explicit, distributed, in-memory application cache for all kinds of data (CLR objects, rows, XML, Binary data etc.)

9. Why? Because you care about any of the following: 1.Performance 2.Scalability 3.Availability

10. Did I mention that “Velocity” is…

11. Where? DatabaseDatabase CloudCloud App Tier Cache Tier Data Tier Potentially expensive read/writes

12. Is it a hassle to install and manage “Velocity”?

13. Installation

14. Regions Logical Hierarchy Region A Key Payload Tags 123 yyyy “Toy” “Chair”.. Velocity Service 123 yyyy “Toy” “Chair”.. Named Cached: Catalog Named Cached: (Default) Regions (Default)

15. What does “Velocity” data partitioning look like?

16. Data Partioning + HA AA CC EEDD BB GGIIHHFF AA CC EE DD BB GG II HH FF Cache Tier App Tier

17. So what happens if one of the servers goes down?

18. Failover AA CC EE DD BB GG II HH FF AA CC EE DD BB GG II HH FF Cache Tier App Tier CC II EE DD CC II AA HH EE

19. Great, so what does the programming model look like?

20. Caching

21. Does “Velocity” provide any concurrency support?

22. Optimistic Concurrency ABC 1. Get2. Get 3. Put 4. Put

23. Pessimistic Concurrency ABC 1. Get/Lock 2. Get/Lock 3. Get 4. Put

24. Concurrency

25. Futures Read-through Write-behind Bulk Access Security Notifications LINQ Queries Cloud

26. Summary Data Types “Velocity”: What/Why/Where? Concepts Features Futures