Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


6 minutes, 8 seconds


Right click “Save as…”

Introducting WACEL - Windows Azure Cache Extension Library.

WACEL implements a number of high-level cloud-backed data structures that can be shared among your Cloud Services, Web Sites as welll as Windows Store applications. You create these data structures just as if you were using local data structures. No APIs to learn, no caching strategies to build, no need to do transient error handlings, no need to manage batches and compressions - just new up the data structures you want to use and code away!

WACEL on CodePlex

WACEL on NuGet

A demo cube using WACEL on Windows Azure


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Great video, thanks!

    By the way, what plugin are you using to display live class and method reference count?

  • Looks like a good abstraction !! I will mess with this soon...

    @eierina: The live code reference count is the new "Code Lens" feature in Visual Studio 2013. You can find more details about VS 2013 here : http://www.microsoft.com/visualstudio/eng/visual-studio-2013

  • Thank you for your interests in WACEL! WACEL is designed to make common scenarios easier. If you have any scenarios that you think that WACEL could be helpful, please feel free to reach out to us by sending a mail to hbai@microsoft.com.

  • ivanivan

    This is very interesting. I have a few questions:
    - How does it scale? Does it rely on Azure or it implements own mechanism.
    - What are the size limits?
    - Is it possible to see utilization/space etc.? Any controls around it, capping the size, etc.
    - How does monitoring/logging work?

    any documentation about its architecture would be useful as well.


  • Hi ivan:

    To answer your questions:

    1. The library itself is stateless, so it scales along with backend services.

    2. The size is limited by backend service, such as the size of your cache cluster.

    3. Because all operations go through the backend service, the existing telemetry, logging and monitor tools are still applicable. However it cold be a good idea to include more metrics counters to provide fine-tuned perf info.

    4. There will be more blog articles and video introductions coming out. Keep tuned!

    Thank you!

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.