Hi, dear FreeBSD community!
Introduction
My name is Ivan. I'm a software developer with a background in Java and C++. Because of the enormous demand for programmers with DevOps skills, I'm working on a daily basis with Kubernetes. But I hate it since when 5 years ago I started working with. Kubernetes is overkill for the majority of tasks(IMHO). But probably my view on the deployments is transformed due to the long work with the tool.
Story
There are a few of my own small pet projects that run on FreeBSD, and I like how it goes. But now I'm going to run my new service, which probably has to be scaled soon. The service stores and manages files over the network. It helps to manage file TV journalists or filmmakers. So the current client demand is 1 TB of space. But for the next one will be on board quite soon after the first one.
The clients upload files not often, it's not a high load service, so probably the one instance can manage 10-50 clients simultaneously. But memory demand is high. So now I know how to do that with volumes in the Kubernetes cluster, but no clue how to manage it with FreeBSD.
Use case
The client is using 1 TB of memory. Tomorrow the client's demand is changed to 2 TB. So I will resize the volume or create a new one. If there are no available resources, I run one more VPS server, then add a worker node into the cluster and create a new volume. The work is done. How the FreeBSD solution would look like?
I'm hosting my services on a local VPS provider in Europe, not AWS, GCP, or DigitalOcean, so EC2 and amazon's balancers are not available to me. Appreciate any advice on how I can manage all of this with FreeBSD, or stop me if it's a crazy idea to manage that kind of cluster for the one-man army.
Thanks!
Introduction
My name is Ivan. I'm a software developer with a background in Java and C++. Because of the enormous demand for programmers with DevOps skills, I'm working on a daily basis with Kubernetes. But I hate it since when 5 years ago I started working with. Kubernetes is overkill for the majority of tasks(IMHO). But probably my view on the deployments is transformed due to the long work with the tool.
Story
There are a few of my own small pet projects that run on FreeBSD, and I like how it goes. But now I'm going to run my new service, which probably has to be scaled soon. The service stores and manages files over the network. It helps to manage file TV journalists or filmmakers. So the current client demand is 1 TB of space. But for the next one will be on board quite soon after the first one.
The clients upload files not often, it's not a high load service, so probably the one instance can manage 10-50 clients simultaneously. But memory demand is high. So now I know how to do that with volumes in the Kubernetes cluster, but no clue how to manage it with FreeBSD.
Use case
The client is using 1 TB of memory. Tomorrow the client's demand is changed to 2 TB. So I will resize the volume or create a new one. If there are no available resources, I run one more VPS server, then add a worker node into the cluster and create a new volume. The work is done. How the FreeBSD solution would look like?
I'm hosting my services on a local VPS provider in Europe, not AWS, GCP, or DigitalOcean, so EC2 and amazon's balancers are not available to me. Appreciate any advice on how I can manage all of this with FreeBSD, or stop me if it's a crazy idea to manage that kind of cluster for the one-man army.
Thanks!