RE: Azure API Management documentation

[Ken Schaefer]

I'm not sure that $39/month or $5/month is "enterprise sized wallets" - I 
suspect most of us here cost that in an hour, let alone a month.

From: ozdotnet-boun...@ozdotnet.com  On Behalf 
Of Stephen Price
Sent: Monday, 20 April 2020 4:12 PM
To: ozDotNet 
Subject: Re: Azure API Management documentation

This is something that annoys me about Azure and its various plans. Discovering 
things missing that should be there or worse, were there but then go away.
Rather than support everything at all levels, they add things that only work at 
higher paid tiers. Its even worse when you start dealing with MSDN 
subscriptions versus paid subscriptions. I found some regions could not deploy 
particular types of products (ie Azure database), despite me having old 
instances of said products already in that region. ie they change things and 
add more restrictions. I'm sure they also remove them. I'm sure there are often 
technical reasons (ie some Data Centers are missing required things to support 
products, but having things disappear from the supported list is annoying).

I think they need to make some smaller instances etc that sit between the free 
stuff and the smallest paid option. For example a website on Azure can be free 
or it can be $39 a month. What about a dotnet core app that could be hosted on 
a linux vm for $5 a month? Last I looked there was no way to run a website for 
$5 a month on Azure unless you do it yourself on a linux vm.

We're not all building websites with enterprise sized wallets.



From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
mailto:ozdotnet-boun...@ozdotnet.com>> on behalf 
of Greg Keogh mailto:gfke...@gmail.com>>
Sent: Monday, 20 April 2020 12:32 PM
To: ozDotNet mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Azure API Management documentation

I have more information. After stumbling around and around the web Portal 
looking for anything related to documentation I noticed a Developer portal 
icon. The help indicates that this is the magic place where API documentation 
is managed, but clicking the Publish button does nothing. 15 minutes later I 
discover that the feature is not available on the consumption plan I chose.

The Basic production plan is ~$200/month which WAY beyond our tolerance levels. 
Our API usage is so low that the consumption plan would have been ideal, but in 
a Catch-22 there is documentation available.

Now I'll just delete the APIM feature and forget it.

GK

Re: Azure API Management documentation

[Greg Keogh]

> We're not all building websites with enterprise sized wallets.
>

Dead right! I often fall into the category between free plan (where things
are missing) and the lowest-end plans which suddenly jump to $20-60/month,
and a few of those really add-up and put a strain on the wallet. We've got
a couple of 64-bit web apps running at the moment, and 64-bit is double the
cost of 32-bit for some weird reason. One of my pending jobs is to get the
32-bit C++ DLL and try to downgrade to save money --
*GK*

RE: Azure API Management documentation

[David Apelt]

I hear your frustration.



I am about to “AWS lambda-ize” a dotnet core 3.1 website and do a
side-by-side comparison with Azure.



https://aws.amazon.com/blogs/compute/announcing-aws-lambda-supports-for-net-core-3-1/



With RDS On Demand
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_OnDemandDBInstances.html
the price may not hit $5/mo but it could get close.



Is anyone else doing that?  (sorry if I am hijacking your conversation
Stephen)



But this is what is tipping me over the edge…
https://serverfault.com/questions/992726/catastrophic-azure-app-service-outage-after-an-automatic-azure-platform-upgrade



Regards



David Apelt



*From:* ozdotnet-boun...@ozdotnet.com  *On
Behalf Of *Stephen Price
*Sent:* Monday, 20 April 2020 4:12 PM
*To:* ozDotNet 
*Subject:* Re: Azure API Management documentation



This is something that annoys me about Azure and its various plans.
Discovering things missing that should be there or worse, were there but
then go away.

Rather than support everything at all levels, they add things that only
work at higher paid tiers. Its even worse when you start dealing with MSDN
subscriptions versus paid subscriptions. I found some regions could not
deploy particular types of products (ie Azure database), despite me having
old instances of said products already in that region. ie they change
things and add more restrictions. I'm sure they also remove them. I'm sure
there are often technical reasons (ie some Data Centers are missing
required things to support products, but having things disappear from the
supported list is annoying).



I think they need to make some smaller instances etc that sit between the
free stuff and the smallest paid option. For example a website on Azure can
be free or it can be $39 a month. What about a dotnet core app that could
be hosted on a linux vm for $5 a month? Last I looked there was no way to
run a website for $5 a month on Azure unless you do it yourself on a linux
vm.



We're not all building websites with enterprise sized wallets.




--

*From:* ozdotnet-boun...@ozdotnet.com  on
behalf of Greg Keogh 
*Sent:* Monday, 20 April 2020 12:32 PM
*To:* ozDotNet 
*Subject:* Re: Azure API Management documentation



I have more information. After stumbling around and around the web Portal
looking for anything related to documentation I noticed a *Developer portal*
icon. The help indicates that this is the magic place where API
documentation is managed, but clicking the Publish button does nothing. 15
minutes later I discover that the feature is not available on the
consumption plan I chose.



The Basic production plan is ~$200/month which WAY beyond our tolerance
levels. Our API usage is so low that the consumption plan would have been
ideal, but in a Catch-22 there is documentation available.



Now I'll just delete the APIM feature and forget it.



*GK*

-- 

 

Level 5, 143 Coronation Drive, Milton QLD 4064 | PO Box 1464, Milton 
QLD 4064
www.transmax.com.au <http://www.transmax.com.au>

 





This
 
e-mail and attachments may contain confidential or privileged 
information. 
If you are not the intended recipient,please notify the 
sender immediately 
by e-mail and then delete this message and 
attachments.  In this instance, 
any distribution,copying, publication, 
or use of this information for any 
purpose is prohibited.

Re: Azure API Management documentation

[Stephen Price]

This is something that annoys me about Azure and its various plans. Discovering 
things missing that should be there or worse, were there but then go away.
Rather than support everything at all levels, they add things that only work at 
higher paid tiers. Its even worse when you start dealing with MSDN 
subscriptions versus paid subscriptions. I found some regions could not deploy 
particular types of products (ie Azure database), despite me having old 
instances of said products already in that region. ie they change things and 
add more restrictions. I'm sure they also remove them. I'm sure there are often 
technical reasons (ie some Data Centers are missing required things to support 
products, but having things disappear from the supported list is annoying).

I think they need to make some smaller instances etc that sit between the free 
stuff and the smallest paid option. For example a website on Azure can be free 
or it can be $39 a month. What about a dotnet core app that could be hosted on 
a linux vm for $5 a month? Last I looked there was no way to run a website for 
$5 a month on Azure unless you do it yourself on a linux vm.

We're not all building websites with enterprise sized wallets.



From: ozdotnet-boun...@ozdotnet.com  on behalf 
of Greg Keogh 
Sent: Monday, 20 April 2020 12:32 PM
To: ozDotNet 
Subject: Re: Azure API Management documentation

I have more information. After stumbling around and around the web Portal 
looking for anything related to documentation I noticed a Developer portal 
icon. The help indicates that this is the magic place where API documentation 
is managed, but clicking the Publish button does nothing. 15 minutes later I 
discover that the feature is not available on the consumption plan I chose.

The Basic production plan is ~$200/month which WAY beyond our tolerance levels. 
Our API usage is so low that the consumption plan would have been ideal, but in 
a Catch-22 there is documentation available.

Now I'll just delete the APIM feature and forget it.

GK

Re: Azure API Management documentation

[Greg Keogh]

I have more information. After stumbling around and around the web Portal
looking for anything related to documentation I noticed a *Developer portal*
icon. The help indicates that this is the magic place where API
documentation is managed, but clicking the Publish button does nothing. 15
minutes later I discover that the feature is not available on the
consumption plan I chose.

The Basic production plan is ~$200/month which WAY beyond our tolerance
levels. Our API usage is so low that the consumption plan would have been
ideal, but in a Catch-22 there is documentation available.

Now I'll just delete the APIM feature and forget it.

*GK*

Azure API Management documentation

[Greg Keogh]

Folks, I'm experimenting with the Azure API Management

feature. I've imported some Functions and I like the concept of being able
to put a façade over different back-end services to make them all look
consistent, and to add monitoring, security and throttling as needed.

Does anyone know the recommended way of documenting the APIs (assuming it's
possible)? I really need to create the Swagger-like documentation that many
people are familiar with. Searches reveal conflicting advice. Some say you
import existing Swagger docs, some say full API documentation is built into
APIM, but I can't find where that is.

Thanks,
*Greg K*