Etcd, or, why modern software makes me sad
roguelazer.com
Etcd, or, why modern software makes me sad
1–10 of 648 posts
Re: Etcd, or, why modern software makes me sad
#2This seems rude and also dishonest/revisionist, eg "In 2015, an unrelated tool called Kubernetes was released by Google (but, really, by Xooglers)".
Re: Etcd, or, why modern software makes me sad
#3"Kubernetes is the worst thing to happen to system administration since systemd."
I'll take that quote into my fortune file.
Re: Etcd, or, why modern software makes me sad
#4This seems rude and also dishonest/revisionist, eg "In 2015, an unrelated tool called Kubernetes was released by Google (but, really, by Xooglers)".
Seriously! This sounds salty AF.
Re: Etcd, or, why modern software makes me sad
#5"Kubernetes is the worst thing to happen to system administration since systemd." I'll take that quote into my fortune file.
What are some of the arguments against `systemd`? I've used it in several production systems and don't really have an opinion on it.
Re: Etcd, or, why modern software makes me sad
#6This just reads as a systems engineer who is angry about new tooling/processes replacing parts of their job.
Re: Etcd, or, why modern software makes me sad
#7I don't experience the sadness that the writer of the blog mentions. However I do understand what they mean. Personally, I've decided I don't really like huge projects, and instead have focused on smaller iOS apps. They don't have dependencies, except for what the Apple platform offers. There's a backend, but it's really abstracted away for me through a RESTful API. And I'm able to continually and without fail, deliver something of value to my customer.
Re: Etcd, or, why modern software makes me sad
#8> the simple internal data model was replaced by a dense and non-orthogonal data model with different types for leases, locks, transactions, and plain-old-keys
I maintain a (/the only?) etcd3 library for Node.js[0], and used etcd extensively on my former team.
None of these things are new to etcd3 API. All of these are present on v2 as well[1], whose API the author extolls, or are built within clients on etcd's base APIs (e.g. there's no 'lock' API, only leases). However, with etcd3 we get stricter typing, better performance, and better semantics (e.g. watch streams and lease streams over polling) thanks to GRPC.
In general these rich APIs allow 'average' engineers to build complex distributed apps more correctly. I've built reliable sharding, hash rings, elections, and so on based on etcd's API--none in more than a hundred or two lines of code (more in Go, less in Node.js). All of these are classic hard problems that etcd makes easy. Sure, there's innumerable standalone services for each of these things, but often there's no need to take the cost of many tools when one would work.
Re: Etcd, or, why modern software makes me sad
#9There's a lot of justified hatred for kubernetes, but for fuck's sake why did anyone adopt it in the first place, if they didn't understand what they were getting into? It's like the startups from 10 years ago who absolutely had to use MongoDB because "scale", and then they never get off the ground because they're trying to implement ACID from first principles.
Re: Etcd, or, why modern software makes me sad
#10Oh man, thank you for this. I cannot stand the engineering culture of Google and I especially cannot stand the engineering culture of Google wannabes. Google ruins everything they touch, and I'm really sick of the engineering worship they most certainly do not deserve. Every single piece of software to come out of Google is overengineered, broken garbage.