Windows Azure Conference 2014

Windows Azure Conference 2014

Anurag SharmaAngshuman Nayak

Caching Data in the Cloud with Windows Azure

Windows Azure Conference 2014

Agenda• What is Windows Azure Cache ?• Why do I need Cache ?• What can I cache ?• Windows Azure Cache Service (preview)• Key differences• Cache features• Client applications• Diagnostics• Key takeaways• Demo

Windows Azure Conference 2014

What is Windows Azure Cache?

A distributed, in-memory, flexible cache for all data types that can be used to speed up Windows Azure applications and reduce database load.

Basically, cache helps your app become faster.

Azure Cache

Windows Azure Conference 2014

Why do I need cache?

Web tier

Data tier

Load on server increases with users

Add a load balancer and more web instances Continue to scale out the web and BI tiers

DB load starts to increase, becomes the bottleneck

LB

BI tier

Windows Azure Conference 2014

Why do I need cache?

Data tier

Cache

Improve application performance

Cache tier

LB

Reduce load on DBWeb tier

BI tier

Windows Azure Conference 2014

• Airline seating charts• Inventory management

system• Game leaderboards• Performance counters• Weather • Stock quotes

• Session state• Shopping cart• Game scores and state• Social feeds• Query output results

• Product catalogs• Employee data• User profiles• Images

What can I cache?

Activity DataRead/Write, created and maintained during a user session

Reference DataRead-heavy, changes infrequently

Resource DataRead/Write, common resource accessed by multiple users

Windows Azure Conference 2014

Windows Azure Cache Offerings

cloudWindows Azure Shared CachingWindows Azure In-Role Cache (SDK)Windows Azure Cache Service (preview)

Windows Azure Conference 2014

Key differencesCache Service (Preview)

In-role cache Shared Azure Caching

Pricing model Memory based VM based Memory based

SLA SLA backed Only on VMs SLA backed

Dedicated infra Yes Yes No

High availability Yes Yes No

Throttling/Quota No No Yes

Size of cache 128 MB to 150 GB*

1 GB to 350 GB 128 MB to 4 GB

Latency Sub-millisecond Sub-millisecond ~5 ms

VM support Yes No Yes

Websites support Yes No Yes

Windows Azure Conference 2014

Cache features• Resilient to Azure updates• High availability• Scalable cache• Local cache• Notifications• Regions and Tags

Windows Azure Conference 2014

Cache features• Get/Put API variations• Pessimistic and optimistic locking support• Zero code ASP.NET session state and output

cache support• Zero code change migration for .Net based

memcache apps• On-wire compression• Custom serialization

Windows Azure Conference 2014

Client applications• NUGET package• Client configuration<autoDiscover isEnabled="true" identifier="[Cache role name or Service Endpoint]"/><!--<securityProperties mode="Message" sslEnabled="false">        <messageSecurity authorizationInfo="[Authentication Key]" /></securityProperties>-->

• Emulator

Windows Azure Conference 2014

Diagnostics• Only client side logs are available to users• PaaS

– No change in logging. Client side logs still go to storage.

• IaaS– Same as on-premises. Logs are collected manually via logman

command.

• WebSites– No access to WebSites VM. Logging relies on .Net tracing.

Windows Azure Conference 2014

Demo

• Portal overview• Cache Client application

Windows Azure Conference 2014

Key takeaways• Microsoft managed, Dedicated infra, SLA backed

• Breadth support– Cloud Services– Azure Websites– Azure Virtual Machines

• Full parity with in-role cache (SDK)

Windows Azure Conference 2014Windows Azure Conference 2014

Customer Interaction Zone (CiZ)

Any question on Anything Azure!

Book your slot now! @ the registration desk at the CiZ

Ask the Experts

GBRDay 15:15 PM

Windows Azure Conference 2014Windows Azure Conference 2014

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.