Windows Azure Integration Pack
Greetings!
Feel free to suggest stories and vote for the existing ones to help us determine what will go in the release of the Enterprise Library 5.0 Windows Azure Integration Pack.
Please note this list may not always represent the actual priority list for the patterns & practices development team. It also does not constitute any commitments.
There are at least 4 pages of stories. Make sure to review all of them.
33 results found
-
Videos: Architectural Guidance
As a developer I want a demonstration in a short video (<15 minutes)of some of the key architectural elements of the reference implementation so that I can quickly orient myself to these elements of the design of the reference implementation.
4 votes -
Diagnostics: cleanup mechanism for WAD tables
As an administrator I want to have a policy-based mechanism to purge the entries in the WAD tables so that I can optimize the usage of storage. The policies should consider kind of entry, severity, age, etc.
13 votes -
Automatic purge to blobs
I need the ability to automatically purge WADLogs to blob storage (hourly or daily - one blob per interval)
8 votes -
Data Access: Continuation tokens management
As a developer, I want the data access block to handle page contiuation tokens for me when the server returns less than the expected rows to me. Especially when the query passes over partition boundaries.
6 votes -
Reference Implementation: Commenting
As a developer I want a reference implementation that has many comments in the code that illustrates and explains how the code works and why it's designed that way.
4 votes -
Developer's Guide: Architectural Guidance
As an architect I want a Developer's Guide that discusses different architectural approaches to use with Windows Azure applications (for example CQRS) so that I can apply architectural good and proven practices to my own Windows Azure applications. The developers guide should illustrate how Enterprise Library supports these architectural best practices.
2 votes -
Diagnostics: move older entries from Azure Storage
As a developer I want my log entries stored in Azure Storage to be transferred to a Remote Logging Service (or any other trace listener) based on the number of items OR age OR absolute size so that I could optimize my logging strategy AND archive my log entries to a on-premises data store.
9 votes -
Diagnostics: remote logging service
As a developer I want to easily forward my log entries to a remote service so that I can reuse my current remote logging service infrastructure.
8 votes -
Voting
Sometimes applications need to determine wheather to take certain action or not by voting on it. All nodes involved need to be able to vote, and the master decides on the final action based on the responses.
2 votes -
Diagnostics: support formatter for system diagnostics listener
As a developer I want to specify a formatter for my log entries that are sent to Azure Diagnostics.
4 votes -
Diagnostics: send entries to queuing system
As a developer I want to send my log entries to a queuing system (Azure Queue, AppFabric Service Bus Queue/Topic, or others - please comment on which queue implementation you're interested in being supported).
4 votes -
Diagnostics: runtime change API
As a developer I want to have a change API for the Logging Application Block so that I can switch to different levels of logging verbosity (from being completely disabled, to logging every piece of debug info).
2 votes -
Diagnostics: rolling mechanism when logging to Azure Storage
As a developer I want to have a rolling mechanism for my log entries stored in Azure Storage based on the number of items OR age OR absolute size so that I can optimize my logging strategy.
1 vote
- Don't see your idea?