Ask HN: Kubernetes Worth It? To paraphrase Phil Greenspan’s famous LISP quote: “Does any sufficiently complicated micro service architecture contain an ad hoc, informally specified, bug ridden, slow implementation of half of kubernetes?” Thought that might be an interesting way of saying is it worth bitting the bullet and spending the effort to understand and use kubernetes. |
After I figured it out, I spent a good month writing personal projects to play with channels and concurrency and get the "these are cool I'm going to use them everywhere" urge out of my system.
Here's a fun experiment: dig through your codebase and find all the public methods, then look at the signatures and find the top 3-5 most common constructs. Now define an interface using those. Perhaps not very useful, but interesting to see. I bet a comprehensive audit of Go code in the wild (not including the standard libraries) would find a lot of types implementing something like this this:
type StringHandler interface {
Handle(string)
Parse(string)
Count() int
}