3 ms·
I agree. The characterization of live reload capability as "table stakes" for availability is nonsense. High-availability designs never require singleton serv
by otterley 8y ago
I agree. The characterization of live reload capability as "table stakes" for availability is nonsense. High-availability designs never require singleton services.
Being able to replace vulnerable singletons that require process and TCP socket gymnastics with multiple instances having good fault isolation properties is the real "table stakes" for modern highly-available service architectures.
- old-gregg 8y ago> The characterization of live reload capability as "table stakes" for availability is nonsense. ... > replace vulnerable singletons You clearly didn't read (or failed to comprehend) the article. Not every protocol on the internet is stateless and no, Teleport is not a singleton.
- otterley 8y agoThe fact that I disagree with your characterization or opinions doesn't mean I didn't read or comprehend the article. Stateful protocols on the Internet are few as a proportion of overall traffic, and it was a wise choice for HTTP to be stateless. This improves its ability to be highly available. Teleport and SSH themselves are absolutely singletons in the most common use case: you want to SSH to the designated server, and that server alone. The service is "ssh on instance X." No other server is an acceptable substitute. That fact makes the service a singleton. Listen, don't get me wrong -- I'm very pleased that you put this article out as it's very insightful. The technical information in it speaks for itself; it didn't need to be burdened with controversial opinion.
- old-gregg 8y agoPerhaps the article was not explaining in detail what this daemon does. No, it's not just an SSH endpoint on instance X. For large deployments it is an SSH gateway (better implementation of jumphost) to your entire data center and it's running on multiple hosts behind an LB. Yet, every instance of it may be supporting hundreds of long-lived SSH connections originating from multiple teams, some of them can be deploying something critically important. So, yes, this socket acrobatics is absolutely table stakes and is required (and has been requested by corporate customers of T) for robust infrastructure upgrades. Old-timers like to refer to this as "carrier-grade" way of doing things. You may dislike SSH itself, but hey - that's what our current UNIX tooling depends on, so we have to make it work, and work well. Besides, even stateless HTTP sometimes needs reliable long-lived connections! Full disclaimer: I'm one of early Teleport contributors.
- otterley 8y agoI don't dislike ssh. It's sometimes necessary and useful. But the modern way of performing deployments is not via ssh -- it's via container and load balancer orchestration and virtual machine management infrastructure. Making your customers happy is good for business, and I salute you for the work you've done in this area. But I still take issue with your "table stakes" characterization and maintain that it is best omitted from an otherwise good discussion. Being "table stakes" for your business is different from being "table stakes" for service architectures generally.