Scaling On The Fly
We've been building a lot of cool stuff, but this week, I just finished working on the scaling and tearing down of a cloud infrastructure. Right now, we're focused on cloud native and so docker containers.
I like to think of Oatfin as a container platform or a simpler, more intuitive, and developer friendly version of Kubernetes. So you can intelligently automate your cloud infrastructure, but also schedule deployments, scale, and secure your cloud native and container workloads on the fly.
This is a demo of the scaling feature. With this feature, developers can specify a desired, minimum, and maximum capacity of workloads or tasks to scale the containers to. The infrastructure then autoscales based on average CPU usage. Another feature I'm working on is exposing the CPU and memory for each task so a developer can change the default values. Right now, the default values are 1GB for the memory and 512 units for the CPU or 0.5 vCPU.
Another feature I just finished working on this week is the tearing down of a cloud infrastructure. This is actually a massive problem with cloud infrastructure because sometimes there are dependencies that have to be stopped or removed in certain order. For example, security group A depends on security group B, so the security groups have to be deleted in the right order.
That's it for this week.
Thanks for reading!