What happens if a node fails?
As long as you have multiple replicas of the pods they keep serving traffic.
Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
21–30 of 159 posts
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#221. Anything that offers effective competition to Kubernetes is a Good Thing. I'm not saying this is because I haven't look at it closely enough but competition brings about improvement. 2. Why do people write "Simplenetes has a 100x less code than Kubernetes" instead of saying it has 1/100th the code?
By contrast, Kubernetes has at least 1000x more developers working on it
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#23Kubernetes might follow the sad path of spring. Perfect, complete and too complex. For big and great applications, spring if the obvious choice. It makes incredible complex and difficult things easy. But, unfortunately, makes simple and quick applications incredible complex and difficult.
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#24Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#25If you're looking for a simple Kubernetes alternative, take a look at the HasiCorp stack. I use that in production and it's easy to set up and maintain.
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#26This is ~17k lines of shell scripting and claims to be "simple". Kuberentes is probably ~1m lines of Go. I'm not entirely convinced that this is less complex (simpler) than Kubernetes. There are many factors in complexity, but a big one for me is what I have to hold in my head – global state. From any given point, what do I need to understand to know what's actually going on. For Go, this is actually comparatively li…
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#27Kubernetes might follow the sad path of spring. Perfect, complete and too complex. For big and great applications, spring if the obvious choice. It makes incredible complex and difficult things easy. But, unfortunately, makes simple and quick applications incredible complex and difficult.
You can't be talking of Spring Framework!? That's a 2000's solution (in particular Hibernate) trying to stay relevant.
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#28Kubernetes might follow the sad path of spring. Perfect, complete and too complex. For big and great applications, spring if the obvious choice. It makes incredible complex and difficult things easy. But, unfortunately, makes simple and quick applications incredible complex and difficult.
You can't be talking of Spring Framework!? That's a 2000's solution (in particular Hibernate) trying to stay relevant.
what would you use these days?
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#291. Anything that offers effective competition to Kubernetes is a Good Thing. I'm not saying this is because I haven't look at it closely enough but competition brings about improvement. 2. Why do people write "Simplenetes has a 100x less code than Kubernetes" instead of saying it has 1/100th the code?
Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
#30This is ~17k lines of shell scripting and claims to be "simple". Kuberentes is probably ~1m lines of Go. I'm not entirely convinced that this is less complex (simpler) than Kubernetes. There are many factors in complexity, but a big one for me is what I have to hold in my head – global state. From any given point, what do I need to understand to know what's actually going on. For Go, this is actually comparatively li…