Hacker News Reader

Comment by kefirlife | Hacker News Reader

OpenFaaS is one option for your functions. Knative is pretty good as well for the bulk of your applications without exposing developers to kubernetes directly. Between that and Crossplane I think you have all the pieces needed to move away to a self hosted solution where you are managing either metal or VMs through a hosting provider.

I’m not sure what this looks like outside of the US, but colocation providers offer racks of machines, or to host your machines, while providing access to cheap bandwidth and peering capabilities. It’s absolutely possible to move away from the major cloud providers. However, it will require a degree of investment within your organization to support these deployments no matter which you choose, which could be a new investment compared to using AWS, GCP or Azure.

View on HN

You need teams of people, the good news is that they're available here. It's not hard as such just requires time and money (quite a lot).

It's not just kubernetes and openFaaS, what about that thing that's a virtual appliance and requires a VM, now you need KVM. Network and firewalls? Storage as in fully replicated cannot ever lose a byte or have it unavailable storage? Object as well as block. Databases, point in time restores/backups/automated maintenance for postgres and then you've probably got a mssql server for that one app, and mysql for that other app.

It becomes just a fairly massive task back in the real world.

OpenStack out of the box does KVM, network, firewalls, NVFs, orchestration (via native heat or terraform), and with the Magnum component can launch k8s, Mesos, or Swarm largely automagically. Storage is typically via ceph (which does block, object [supports Swift/S3 protocols] and filesystem) and supports snapshots and is fully replicated. Sadly the managed database service didn't make it far, but with Heat or Terraform it's pretty easy to spin up a VM holding your DBs. The native FaaS service, Qinling got deprecated a while back. Secrets management via the barbican component. Web interface via the horizon component.

I'm not too familiar with the whole range of AWS offerings, but I really think aside for DBaaS and FaaS OpenStack can cover pretty much everything someone would need, especially combined with Ceph for storage.

All opensource.

Yes, I'm aware. It doesn't reduce or negate the need for a team responsible for running storage and understanding how it works, then a team owning databases (probably with some development resources too) and so on.

It actually takes work to setup and run we are not just installing some packages and then pretending you can scrap aws.

AWS EBS volumes (except io2) have an annual failure rate of 0.2%, so if you have 1000 running statistically you will loose 2. For io2 it's 0.001%, but still not 0.

io2 high durability is 1 in 100,000 per year.

S3 has 99.999999999% durability as standard.

I see your point that it's not technically 100% but, as close as can be reasonably achieved.

That is why you have snapshots on S3

Check out longhorn which offers replicated iscsi or nvme for free on your hardware. What you say is not that hard to do, if you want to do it.

Reply on news.ycombinator.com