41–50 of 159 posts
Earlier quoted context omitted.
First time I'm hearing of space also. It looks quite impressive, surprised to see no stars
Thanks! We just moved Space.sh from GitLab to GitHub (hurts in my heart, but yeah community is on GitHub). Also we are lousy at promoting our stuff, maybe April 1st is not the best day to do this either...
I'm surprised when people say this. I thought communities were only around repos.
This 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…
edit: wc reports 47023 lines in *.sh[1], out of which 23836 are unique[2].
[1]: find . -name '*.sh' | xargs cat | wc -l
[2]: find . -name '*.sh' | xargs cat | sort | uniq | wc -l
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?
[1] - https://quarkus.io/ [2] - https://micronaut.io/
Bulk of complexity in opensource distro of kubernetes comes from the fact that everything is interface driven and has to work in an generic way. For example, you don't really have to implement cri-o like thing if you are opinionated platform and only supports docker. Similarly, you don't have to build CSI, if you only support ceph or aws' storage. I love the contrarian thought, but matter of the fact is modern orchestration platforms that want to be a general purpose platform is going to be big.
It is a really nice exercise however build something like this when you want to learn about networking, containers, orchestration, storage etc. and how to tied everything together.
If 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.
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?
Now I’m trying to figure out if I just got too old to appreciate them, or if the good ones have all been used up.
Building a platform to deploy stateless services are the easy part. This might even work nicely at a smaller scale. It is gets super complicated when you want to mount volumes, re-use those volumes. This is like a nice weekend project, contrarian in nature, but it is just not a replacement for kubernetes. This is some bash script orchestration on top of podman. Bulk of complexity in opensource distro of kubernetes co…