Live data from Hacker News

Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

github.com

71–80 of 159 posts

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#71
The amount of vitriol in this comments section is astonishing. Can we not share fun projects without the professional Kubernetes experts thumbing their noses? At the very least, it does seem now like the complexity of K8s’s code base is a point of very thin skin for the community.

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#72

This is really cool, but is there a real use case for this?

Thanks :) The real use case is super simple clusters, which could be just 1 node, no etcd, no API (SSH managed), no iptables. Simplenetes is not a living breathing thing which auto heals it self, it's a deterministic approach where you can see your cluster with all hosts in the git repo which represents the cluster. Also, it's focused on making local development easy, so you can develop in a micro services architectu…

> clusters, which could be just 1 node

Despite whatever the k8s crowd misuses the term to be, 1 node is not a cluster. It might be a single node managed using cluster-capable technologies, but it's still not a cluster.

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#73
post #28

Earlier quoted context omitted.

You can't be talking of Spring Framework!? That's a 2000's solution (in particular Hibernate) trying to stay relevant.

Asking to learn, but if you were to start a Java application in the following two scenarios: 1) Monolith with some CRUD, API, persistence to a DB + search. 2) Scalable backend with an API, persistence to a DB + some caching what would you use these days?

HTTP: javalin

persistence: jooq + postgres

search: postgres full text search

cache: ehcache

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#74
17k lines is a lot of shell... but... it bypasses all the complexity of heavyweight scripting languages, bash is a lightweight interpreter that is always there and just works and i bet it's fast.

this is a cool idea.

next up, somebody will modernize daemontools for the container/cluster era...

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#75
post #74

17k lines is a lot of shell... but... it bypasses all the complexity of heavyweight scripting languages, bash is a lightweight interpreter that is always there and just works and i bet it's fast. this is a cool idea. next up, somebody will modernize daemontools for the container/cluster era...

i must say though, i'm not sure how i feel about a shell script "daemon"...

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#76
post #6

Not April fools judging by github history...

Thank you for noticing! :) Yeah, this represent a few months of full time work.

So you’ve worked on it for like a 1000 hours and shared it for free?

How can you afford this?

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#79

The whole setup of github project looks like it is a serious attempt.

Anyone taking up 17KLOC of shell script “as is”, regardless of how many cool domains it is on, to use in production deserves everything they get subsequently.

It will be a useful learning experience.

The same goes about taking up k8s with no thinking, by the way.

Re: Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script

#80
post #2

> simple > 17k lines of shell script those two phrases don't belong together... to think about this, "17k lines" and "shell script" should not be used together either. Also, you are a bit light on tests.. there only seems to be a single trivial one, which seems way too low for a codebase this size.

i dunno. autotools is hairy, but it also solved some incredibly hairy problems over an enormous breadth for a very long time in a very reliable manner.

portability across all the different unices with their weird c compilers and differing libcs that actually worked out of the box every time was a gargantuan task.

Post reply on HN