Blog Post

Meet WACEL

Sign in to queue

Description

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

Embed

Download

Download this episode

The Discussion

  • User profile image
    eierina

    Great video, thanks!

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

  • User profile image
    jomit

    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

  • User profile image
    Haishi.Bai

    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.

  • User profile image
    ivan

    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.

    thanks!

  • User profile image
    Haishi.Bai

    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!

Add Your 2 Cents