Chris Auld

My feedback

  1. 51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Chris Auld commented  · 

    Without this we have to parse our message body... which has the potential to error. being able to tag it with metadata would allow us to have a more ''guaranteed' mechanism for retrieving a correlation Id which we can then use to debug parsing problems. So +1 to this from me.

  2. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Chris Auld shared this idea  · 
  3. 1,167 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    Chris Auld commented  · 

    Hi Calvin. Thanks heaps for the update. The load-balancer based workaround doesn't really solve the problem because a key goal of this is cost management; we'd still be paying for the Hot standby. The goal is to shut it down and undeploy so as to not be billed for it.

    Chris Auld shared this idea  · 
  4. 2,246 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    74 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.

    For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

    Chris Auld commented  · 

    Blob storage is, in effect, a big massive scale static web server. THis makes it very suitale for directly serving certain types of static web sites that may be hit by a big spike in load. The one statis web server feature missing that is really hard to work around is a lack of a default document.

    It should be possible to set a single blob in each container as the default blob and this should be returned if the HTTP GET request provides only the container name.

    This would allow
    http://myservice.blob.core.windows.net/
    and
    http://myservice.blob.core.windows.net/mycontainer/

    Chris Auld supported this idea  · 
  5. 1,386 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    83 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Chris Auld commented  · 

    Just be careful with this feature though folks. It is often a much better idea to duplicate the relevant data using a different partition key. This allows for more efficient querying as partitions always live on a single storage node.

    For small scenarios just use SQL Azure. For large scale out scenarios you really don't want to do a query that requires the fabric to retrieve your data off 10's or 100's of storage nodes.

  6. 1,212 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    57 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →

    Windows Azure Websites offers the ability to have smaller deployed websites. The ability to have multiple roles on a single VM instance is still in planning.

    Chris Auld commented  · 

    This is doable. But I agree with Joannes re seperation of concerns.
    Azure isn't really targeted at small workloads.

    This specific requirement is very doable today.

    Worker Roles: Use Lokad.Cloud... This should be a part of every Auzre devs toolkit IMHO

    Web Roles: Examine the host headers to determine which web app is being requested (CName all your apps at your *.cloudapp.net record). Then use a Virtual Path provider to load the content out of Blob storage. Voila... SharePoint like goodness running in Azure.

Feedback and Knowledge Base