Simon Luckenuik

My feedback

  1. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Functions » Feature  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  2. 70 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Azure Functions » Feature  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik commented  · 

    I will copy here some comments I made previously on GitHub (https://github.com/Azure/azure-functions-host/issues/2557) to provide some arguments in favor on that approach:

    Using Azure Functions V2, I was able to have Razor Pages running properly inside a Functions host using the TestServer approach: http://www.luckenuik.net/hosting-your-aspnet-core-razor-pages-inside-azure-functions/

    This is a proof of concept, but if we develop something similar to TestServer of production grade (and proper tooling to ease the job), we should be able to leverage the full power of MVC APIs\Pages inside Azure Functions.

    I do understand that Azure Functions is meant to target multiple languages and that this is a .NET only approach, but I believe there is a need for such an approach. Obviously, something built-in Azure Functions would be preferable...

    I know there are some people out there against running AspNet Core MVC inside Azure Functions, but the complete discussion around "it will take more memory, increase start-up time and adds overhead" is meaningless in my view, at least for some scenarios:

    -Startup time: we are already facing Cold Starts today, that's not going away, adding few milliseconds to initialize the MVC stack is irrelevant. With Azure Functions Premium plan, these concerns will be less relevant, I guess.

    -Execution Cost: No matter how much memory you are using, for some apps it is still cheaper than having an App Service running 24/7.

    -Ramp-up Cost: It is way cheaper to take the existing knowledge of developers and make them code as usual with MVC Controllers instead of ramping-up with Azure Functions.

    -Reuse Opportunity: A lot of work was done by different projects to increase the AspNet Core middleware with interesting features (Ex: Authn\Authz), it is a shame that we cannot reuse that work easily with Azure Functions.

    -Complexity: If you want to run any business application on Azure Functions, you will face complex code that might take longer than 50 milliseconds. It's not true, in my view, that Azure Functions was designed for small projects only, with quick "in and out" only.

    Simon Luckenuik commented  · 

    That would help minimize ramp-up time for developers coming from the Web API world.
    This would also ease migration of some API based applications to Azure Functions.

    Simon Luckenuik supported this idea  · 
  3. 7,253 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    193 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik commented  · 

    Managing Let's Encrypt renewals manually is painful, please integrate it. Azure is already providing free SSL Certificates for CDN, let's make it globally available in Azure!

    Simon Luckenuik supported this idea  · 
  4. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  CDN  ·  Flag idea as inappropriate…  ·  Admin →
  5. 340 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  12 comments  ·  CDN  ·  Flag idea as inappropriate…  ·  Admin →
  6. 51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  CDN  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Anton Kucer [MSFT] responded

    Work has started on both moving capabilities that are only available in the CDN Supplemental Portal (e.g. rules engine) into the Azure Portal and also providing API’s to support all of these features. This work will be done in multiple phases over the next several months.

    Simon Luckenuik supported this idea  · 
    Simon Luckenuik commented  · 

    What is the current status for this improvement? Configuring CDN rules manually is tedious and error prone.

  7. 152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Storage  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  8. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  CDN  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Rule approval is currently automatic with no delay. We will follow up on having the 4 hour approval message you see in the CDN supplemental portal updated to remove this confusion. While approval is automatic it can currently take 90 minutes for updates to propagate to all CDN POPs. Work is under way to significantly reduce this to a much lower value in the next few months.

    Simon Luckenuik supported this idea  · 
    Simon Luckenuik commented  · 

    According to this issue, the approval is still a manual process: https://github.com/MicrosoftDocs/azure-docs/issues/13983#issuecomment-416395573

    Yesterday, I posted updated a rule against a Verizon Premium CDN that took over 8 hours to be approved.

    The rule tester UI would enable us to test the rules prior submitting it. It could be something very simple, enter a URL + Request Headers, run the rules and provide the returned response headers and destimation of the request in the Source.

    Currently, to figure out if something I want to do would work as expected, I have to figure out the rule syntax, add it, wait between 10 minutes and 8 hours, test to see if it works, repeat if not working. A real pain.

  9. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CDN  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik commented  · 
  10. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Maps » Feature requests  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik commented  · 
  11. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Security and Compliance  ·  Flag idea as inappropriate…  ·  Admin →
  12. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Simon Luckenuik supported this idea  · 
  13. 473 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Additional Services  ·  Flag idea as inappropriate…  ·  Admin →
  14. 4,567 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    140 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.

    Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at azurestoragefeedback@microsoft.com.

    Simon Luckenuik supported this idea  · 
  15. 2,656 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    65 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  16. 291 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Azure Cosmos DB » Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  17. 753 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    56 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  18. 465 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
  19. 203 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Azure Cosmos DB » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  20. 739 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is

    1. Store every version/change as a separate item
    2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.

    You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live

    Simon Luckenuik supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base