Earlier quoted context omitted.
Yes, the billing is specifically targeted around per-second execution. The containers can start within a few seconds, they allow for customization of CPU cores and memory, and they allow you to focus entirely on your container without having to worry about any VM management. Traditional VM-based infrastructure is still the way to go for long-running applications. This just opens a new avenue into using containers in…
What would be some example use cases for this?
Azure Container Instances
71–80 of 117 posts
Re: Azure Container Instances
#72If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
You can try for free for up to 1 hour (no credit card required!) at https://functions.azure.com/try.
(I'm a product manager on Azure Functions)
Re: Azure Container Instances
#73Earlier quoted context omitted.
Yes, the billing is specifically targeted around per-second execution. The containers can start within a few seconds, they allow for customization of CPU cores and memory, and they allow you to focus entirely on your container without having to worry about any VM management. Traditional VM-based infrastructure is still the way to go for long-running applications. This just opens a new avenue into using containers in…
What would be some example use cases for this?
Re: Azure Container Instances
#74Companies 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…
It seems to me like it's supposed to be a more flexible, versatile equivalent of AWS Lambda: fired up for a quick operation based on some trigger, then immediately shut down. From that perspective the pricing doesn't seem too bad.
Re: Azure Container Instances
#75Re: Azure Container Instances
#76If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
The main limitation with lambda is really still code size. 50mb is tiny for all but trivial apps thanks to libraries.
(Disclosure: I'm a product manager on Azure Functions.)
Re: Azure Container Instances
#77Companies 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
#78I find it funny to see containers landing in Windows. While I fully approve the containers on Linux, to me it looks like Windows does not really need them: it already has a stable notion of executable files with full binary compatibility. An old but gold EXE format is your container. Please excuse my probable naivety, but am I missing something?
Re: Azure Container Instances
#79Companies 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…
But Hyper.sh is still competitive, I think, even though it's super young. They already have a high level AWS Lambda alternative (Hyper Func) that uses containers and is fully language agnostic, and they have reasonable pricing-per-minute figured out. 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 stuf…
The vision is to merge PaaS into IaaS, e.g. a microservice-native cloud. I want to ask more details of the upper-layer features you imagine. Thanks!
Re: Azure Container Instances
#80So, 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…
I wanted to see this in context but couldn't find it. Is the word "serverless" used in the article?