Have a smaller unit size (i.e. for lab/demo environments)
Stream Analytics is great - but it's a bit much to pay for a full unit hour when you have very low processing requirements. I've got a couple demo and lab environments I'm working with now and have to keep stopping the jobs as each costs about $80/month to run.
The simplest fix for this would be to have a smaller unit size ("shared" unit?) to make it easier to get started with projects.
we will consider this request.
The current cost makes it very prohibitive to test a small load for a long period to see if it’s running correctly and will not fail when deployed. This has been trouble for us with several small clients looking to develop an iot device/solution.
I have the same issue. I have an MSDN subscription which gives me AUD$70 / month to test / learn with. One stream analytics job kills that budget so i am not able to test / learn stream analytics. I lower price point for demo / testing scenarios is needed.
Thanks for the feedbacks. In order to reduce cost, it is possible to use 1 SU for small jobs (this is about $80 per month).
1 SU jobs are able to have different sources, sinks and query steps. So it's actually possible to pack various queries inside 1 job.
So I have an IOT device sending ~50 number every 10 minutes - cost of mobile phone account $10/m. ok.
Data is sent to Azure IOTHub - cost $37/m. ok.
Stream Analytics sends the data to PowerBI - cost $340/m. Outrageously not ok.
Power BI runs dashboards, output is so low that Power BI is free.
Eric Malamisura commented
The pricing is a bit ridiculous to be honest.
I'm using two Stream Analytics jobs to run my home (custom dev) IoT system. Due to the price increase, Stream Analytics is getting too expensive for this scenario. The two jobs are only using a fraction of Unit, but I'll have to pay for two full units each month.
It totally understand you guys need to make money, and I happily recommend Stream Analytics to customers in real-world IoT scenarios. But it would be great if Stream Analytics would become an affordable option (like $10 per job/month) again for hobbyist scenarios too. Just some ideas:
- a smaller (more granular) Unit
- no SLA
- restrictions on functions
- capped performance