2,886 karma · joined April 23, 2008
http://deepaksingh.net
email: deesingh [AT] amazon DAWT com (for AWS related stuff) or deepak [AT] deepaksingh DAWT net (for everything else)
twitter: @mndoci
This is just what I've been looking for. I never warmed to Max for Live for mods. But the extensions SDK I can get behind.
Tesla deserve all the credit for getting everyone else to wake up. But they are so so at making a car I actually want to drive.
The Cloud Control API is an API to the resource model. It unlocks the ability for AWS teams to contribute to the resource model without having to worry about the rest of what Cloudformation does. As a service owner interested in contributing to other systems like TF and Pulumi, now I just have to contribute to one thing. In the medium/long term it's going to be a lot more efficient way to evolve how we all use AWS resources in our favorite Infrastructure-as-code systems.
Disclosure: Work at AWS (but not on the CloudFormation team)
On Fargate, you got the answer there.
Alternatively there’s a lot of algorithm/classifier development you could jump into.
It’s usually easier going the other way though. Biology is a complex beast.
I've always felt there were a lot of background tasks that just need to be done but have no time sensitivity that could fit this model, but in reality it hasn't ever been something you can generalize to a point that it's worth building it out. Still haven't given up on the idea though :).
Each Fargate task has its own isolation boundary and does not share the underlying kernel, CPU resources, memory resources, or elastic network interface with another task. (Source: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...)
The other part is patching. We are (I work at AWS) responsible for patching the underlying hosts. More details at https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...