I have two API Managements created in Azure. One for DEV and the other for PROD. Both are "Basic" Tier
I have many APIs in each of them. I want to divide cost for each "Cost Center" in my organization.
The best way to do this is by number of requests? I think yes, but I will listen recommendations
But what is the best way for this? For example, one API consumes the 80% of the total requests... So this API will pay the 80% of API Management cost. I have to divide cost manually?
Thanks
It depends on definition of a Cost Center. In order to get the number of request per API, Product or Subscription, use the report API.
I would suggest to split costs into infrastructure, development and operation categories.
Infrastructure could be based on number of requests
Development are one time costs based on complexity of the APIs. They have clear business owner=Costs center.
Operation are recurring costs you have with support and bugfixing of the APIs and the API Management. They could be derived from the development costs (for example 20%).
Related
I need to devise a pricing strategy for a SaaS product I plan to go live with, as tricky a task as that is.
Putting product 'value' and things like RoI aside (since they're off-topic here), I'm looking for some assurances against a situation whereby my competitively priced product incurs losses because of increasing blob storage/SQL costs in Azure.
In a nutshell, this web app will allow users to create tasks, to which they may attach any number of hi-res images, documents etc.
So, in order to keep this question specific and technical, what services does the Azure platform offer that helps mitigate against escalating costs of data/blob storage? Or which services lend itself to managing these losses/costs?
For example, I think a DTU option for my SQL Server will be a flat rate as opposed to a dynamically priced VCore alternative. So I could opt for DTU so I at least know where I stand.
Question/s
Does Azure offer flat rate services for storage? Would IaaS instead of PaaS give me this?
Does Azure ofer flat rate for SQL Server? (Is my understanding of DTU correct?)
I'm a bit confused by Azure price calculator. In particular it doesn't explain the bandwidth pricing.
I'm considering Azure for a restful api that is going to use blobs for most data storage together with a sql server database for a subset that is easier to manage with a relational approach.
In this application a lot of data will enter the system through the ReST api, but a small fraction will be exposed to the clients (mainly as summary reports). Still the total bandwidth required should be in the order of 50 GiB/mo.
In the Azure's pricing page related to data transfer I see the pricing is only related to outgoing data, but I cannot figure how this relates to a ReST api that will be hosted in Azure App Service.
I mean, it could just mean that I'm going to pay for the bandwidth consumed by HTTPS responses (and not by HTTPS requests), but it seems a bit hard to estimate what this pricing is going to be.
Within a given region, there are no transfer costs at all. You mentioned using App Service, blobs, and SQL Database. As long as those services are within a single region, there are zero bandwidth costs as data flows between them and any other service within that region.
Bandwidth is billed specifically for outbound transfer. So, essentially you're metered for all data leaving a given region.
If you look at the page Data Transfers Pricing Details
Data Transfers refer to data moving in and out of Azure data centres other than those explicitly covered by the Content Delivery Network or ExpressRoute pricing.
Inbound data transfers
(i.e. data going into Azure data centres): Free
Outbound data transfer prices are set at a sliding scale depending on location and bandwidth used.
inbound traffic is free so the data coming in can be removed from the equation. Outbound is not free, and you saw the pricing page.
Data transfer is everything that is going out from every operation you execute.
And it is hard to estimate the traffic pricing - i would recommend to register the Azure trial and test it for a month and see how it is going. Because your data is not only what is returned, there is a lot of payloads coming with that.
But if you estimate 10 GB/month of outbound traffic, then it will start from $0.087 per GB starting from fifth GB (because first 5 are free). There are different regions described at the pricing page as well, so you should apply the pricing according to the region where your website is.
Right now I have a small web app hosted on Azure services. Its 5 asp.net pages, 1 sql DB, and 2 scheduled jobs. Just through testing, I used 2 dollars of the 220 dollars credit they give you for signing up.
The problem I'm having is that there is no clear pricing guide for the pay-as-you-go service they offer. My live testing was very very lightweight (10 page hits, maybe 50db transactions, and 10 job runs) and its already cost 2 dollars. The breakdown available makes it clear where that money has gone (the scheduled jobs), but doesnt make it clear how much additional usage may cost me going forward.
Is there any area in azure, or any service anywhere, that can estimate the total cost under various loads? I am very hesitant to open this service up to the public until I know exactly what the costs will be, as right now the site brings in 0 revenue, so it wouldnt be worth paying a ton of money just for hosting until I get a revenue model set up.
Sure - use the Azure pricing calculator - http://azure.microsoft.com/en-us/pricing/calculator/
I have actually pay-as-you-go plan in my account right now and I am using free 20MB database to all my projects in this account. I've created mobile services for my mobile app and it's time to release this project. So I think the best for me right now is move from Free Mobile Services to Basic so I can have unlimited devices to use this. But I don't know how much database size and bandwidth I would need. I just want to set my plan to Basic and create new database and then pay how much bandwidth and database size I would need.
I found this calculator and I just want to buy that Basic services with 1 unit and I just don't want to fill any other things (not because I don't want them because I just don't know how many and that it would be great that with rising app using there would be rising too). Is it possible?
I hope I explained my problem well.
Btw: What unit means in "1.5M API calls per unit"?
Thanks
Yes, you can continue to use Free SQL DB with Basic tier of Windows Azure Mobile Services. SQL and Mobile Services are separate items on your subscription and each can be scaled independently of the other. In practice if you have a lot of load, you will likely need to scale both - for architectural reasons.
Egress bandwidth for Mobile Service responses to the client is included in Mobile Services pricing. If you don't use SQL in the same data center, you may incur separate bandwidth charges. Although for latency reasons, we strongly recommend using a database and Mobile Service in the same data center which also eliminates egress costs for Mobile Service - SQL interaction.
You can purchase 1-6 units of Basic tier of Mobile Services. Each unit provides 1.5M API calls per month. So if you buy 2 Basic units, you will get 3M API calls per month and so on.
Thanks.
Dinesh Kulkarni
(Program Manager, Windows Azure)
i have an idea of putting my blog on to Azure instead of a regular webhosting company.
The only thing i cannot figure out is if that will be cheaper or not. The good part is the getting-knowledge of Azure but on the other hand it is my personal blog and i really don't wanna spend to much money on it.
So do you have any idea of how the pricing works? I saw some calculator but didn't manage to understand the numbers.
Thanks in advance
You'd have to have a significantly-active blog to justify the costs of Azure. Aside from keeping a web role up and running (and just one instance chews up almost $90 monthly, as ZippyV stated), you'll also have to pay for data.
You do NOT need to invest in SQL Azure though. There's Azure table storage which is much better suited for your blog. It has a table structure, you can define entities (e.g. classes, maybe a BlogEntryClass) that are stored, and the storage costs will run you significantly less than SQL Azure (only $0.15 per GB per month, so your storage costs will likely remain well under a dollar a month for a blog, a small fraction of the cost of SQL Azure).
You'll also pay for bandwidth ($0.15 outbound per GB).
If this is a learning exercise, it's a great investment, but if you have an MSDN Premium account, you can host your blog there - you get 750 compute-hours monthly (enough to run a single role instance 24x7), 10GB table storage, and 14GB monthly outbound data.
Classic webhosting will be a lot cheaper for you. In Azure you need to pay for at least 1 instance (webserver) to run per hour. At then end of the month you will have to pay about 89$ if I remember correctly and that's without SQL Server.
If you want to learn more on how to develop for Azure you can download the SDK and run your project locally. You don't need to pay for it.
EDIT: you can find the pricing here. If you want to add SQL server you pay a minimum of 100$ a month.