Companies like Hyper [1] should be put on notice. This is a surprisingly unique product. AWS ECS and GKE both require some form of management of the underlying VM. A lot of that management is abstracted away, but not in the same way this is. That being said, pricing [2] seems odd. At $0.0000125/GB_Second and $0.001/Core_Second, lets say you want to replicate an Azure A3 instance (4core/7gb/$130). That would cost... o…
Azure Container Instances
21–30 of 117 posts
Re: Azure Container Instances
#22Does anyone know what service discovery, network security policy and ability to add multiple redundant copies of the same service this offers? I'm guessing it's powered heavily by kubernetes, so maybe that answers the question, but I'd be interested to know more about the details.
Re: Azure Container Instances
#23Companies like Hyper [1] should be put on notice. This is a surprisingly unique product. AWS ECS and GKE both require some form of management of the underlying VM. A lot of that management is abstracted away, but not in the same way this is. That being said, pricing [2] seems odd. At $0.0000125/GB_Second and $0.001/Core_Second, lets say you want to replicate an Azure A3 instance (4core/7gb/$130). That would cost... o…
Re: Azure Container Instances
#24Companies like Hyper [1] should be put on notice. This is a surprisingly unique product. AWS ECS and GKE both require some form of management of the underlying VM. A lot of that management is abstracted away, but not in the same way this is. That being said, pricing [2] seems odd. At $0.0000125/GB_Second and $0.001/Core_Second, lets say you want to replicate an Azure A3 instance (4core/7gb/$130). That would cost... o…
Re: Azure Container Instances
#25If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
Re: Azure Container Instances
#26So, are we just now using “serverless” to just mean “dynamically scalable” the same way that “cloud” used to? Because, previously, “serverless” seemed to mean not needing to deal with anything lower-level infrastructure than function calls (that is, a higher level of abstraction than even a classical PaaS like GAE managed runtimes), while container hosting, dynamically scalable or not, is somewhere between classic Ia…
1. Invisible infrastructure
2. Microbilling
3. Event-based programming model
ACI offers 1 and 2 without forcing 3, thanks to containers.
Re: Azure Container Instances
#27If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
Since you can basically run anything that fits inside a container, the comparison with AWS Lambda doesn't seem relevant to me. If you really want to draw a comparison with AWS product, it's pretty much a serverless EC2 ECS.
I'll give you an example - When I first discovered Lambda I had been working with containers for 6-8 months already and when I saw lambda it hit me that they just have container images capable of running python and node projects that this spin this up in and run the code we ask them to.
My mind immediately then went to our data pipeline that I'd like to run on a nightly schedule. This is typically done using a tool like Airflow or Luigi but I thought I could probably even just build the whole thing in lambda tasks that trigger via cron and SQS.
The reason we ultimately did not do that with Lambda was because it limited the amount of A. time and B. Compute resources one lambda task could use and we did not want to try to optimize for that when working with increasingly large amounts of data.
With something like this (ACI) I could actually do exactly this and even if its triggered by something like Airflow or Luigi I could run those on a much smaller instance and save the larger compute problems to being done on ACI in small spurts
Re: Azure Container Instances
#28If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
Re: Azure Container Instances
#29Companies like Hyper [1] should be put on notice. This is a surprisingly unique product. AWS ECS and GKE both require some form of management of the underlying VM. A lot of that management is abstracted away, but not in the same way this is. That being said, pricing [2] seems odd. At $0.0000125/GB_Second and $0.001/Core_Second, lets say you want to replicate an Azure A3 instance (4core/7gb/$130). That would cost... o…
Looks like they have conflicting data on that page. Further down it quotes "$0.000013 for every Core-s used".
Re: Azure Container Instances
#30Companies like Hyper [1] should be put on notice. This is a surprisingly unique product. AWS ECS and GKE both require some form of management of the underlying VM. A lot of that management is abstracted away, but not in the same way this is. That being said, pricing [2] seems odd. At $0.0000125/GB_Second and $0.001/Core_Second, lets say you want to replicate an Azure A3 instance (4core/7gb/$130). That would cost... o…
They also have open sourced their tech [1], so for certain companies they probably are compelling.
Perhaps they should provide the kind of ease-of-use on top of the stuff they already provide that will cut open a steady market for them, like a Heroku but with this underlying tech and thus more dynamic on scaling and flexible on tech stack.
[1] https://github.com/hyperhq/runv is one example