Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Kubernates in Node.js

github.com

Post reply on HN
Print view View original

51–60 of 71 posts

Re: Show HN: Kubernates in Node.js

#51

Post by cjk »

remram wrote: post #20

I would really welcome more experimentation in the cluster process management space. Right now it's Kubernetes, Nomad, or solutions embedded into applications (e.g. cephadm). It's a shame that this is an exact copy in a different language. Kubernetes is nice but I can't wait to see what the next generation of tools will look like.

I really wish Flynn[1] had taken hold before Kubernetes became so popular. Deploying and managing apps was a hell of a lot less complex, and very Heroku-like.

Sadly, it's no longer being developed as of 3-4y ago.

[1]: https://github.com/flynn/flynn

Re: Show HN: Kubernates in Node.js

#56

Post by robertlagrant »

davnicwil wrote: post #44
robertlagrant wrote: post #32

Earlier quoted context omitted.

What's strange is Docker Compose is very slowly resurging. I almost feel like that with a few more primitves (e.g. nodes with tags) and you'd have a much simpler Kubernetes. Which a lot of people might like.

isn't the whole idea of docker compose that it's supposed to be single machine, though? How likely do you think the introduction of a nodes primitive is given this? I can see it if it were a strict opt in addition but it feels like it also fundamentally expands the scope of what the tool is.

I agree it would, and I think it's unlikely, but I also think there's a gap between Docker Compose and Kubernetes, and while I know the implementation gap is large, the configuration syntax gap is small. If someone could extend the Compose syntax to include some sort of way to declare what node tags it should/shouldn't run on, and how many, it might be really interesting as a good power for config complexity tradeoff.

Re: Show HN: Kubernates in Node.js

#59

Post by mst »

megapixel99 wrote: post #49
mdaniel wrote: post #5

depending on what, exactly "bash commands don't work" https://github.com/Megapixel99/nodejs-k8s/blob/master/functi... > is talking about, but a thing that bites A LOT of folks when dealing with command: [] (and its args:[] friend) is that they are exec style, not "sh -c" style as one might experience with a Dockerfile RUN command. I think Dockerfile's RUN [""] syntax is also exec style, but I don't use it much becaus…

Off the top of my head I do not remember what the issue was (the changes to the code are from a month ago). Looking at the code now, `dockerExec` https://github.com/Megapixel99/nodejs-k8s/blame/master/funct... > uses `child_process` so that may have something to do with it... however, as I have said in other replies, I just wanted to learn more about the inner workings of k8s and I personally learn best when I create…

I may read the source code to your project for fun.

If you ever feel inspired to do so, I *really* wish somebody would write a decent way to do controllers in JS rather than golang (metacontroller is a lovely idea but somewhat limited in what you can build with it).

Re: Show HN: Kubernates in Node.js

#60

Post by _akhe »

paulddraper wrote: post #58

Kubernetes in Node.js: Five comments about how stupid this is. Kubernetes in Rust: Straight to the top

Haha so true. I noticed there's a part of HN that hates JavaScript and NoSQL.

Usually for bad reasons like a false dichotomy between SQL & NoSQL (you usually want both) or some performance comment about JS when they're using like a Rails, Django, or Laravel (some old/slow cult framework that doesn't hold a candle to Node).

Feels like Rust found its place with Next.js' Turbopack (basically Webpack but in Rust), and is good for use cases like that. I think reinventing wheels in other languages makes sense when they bring obvious value like performance or some convenience - and this Show HN fits that description.

Like someone else said - it might've been even cooler as not a re-write but a new approach in Node.

I would love to see Node eat more of Linux personally. To me JavaScript is like the "English" of programming (C is "Latin"?), with JSON being the standard transfer format and the browser being a major (if not the major) platform. Not to mention it's by far the most performant of the dynamic web languages (compared with PHP, Ruby, Python).

Post reply on HN