4 ms·
Given the complexity of the system, I'm curious to know how many people maintain this service
by leakyabstxns 2y ago
Given the complexity of the system, I'm curious to know how many people maintain this service
- rshrin 2y ago5 people (who also maintain a lot of other services like the linked TimeSeries service). The self-service to create new namespaces is pretty much autonomous (see attached link in the article on "Provisioning"). The stateless layer auto-scales up and down based on attached CPU/Network-based scaling policies. The exports to audit stores can be scheduled at a cadence. The only intervention is when we have to scale the storage layer (although parts of it also automated using the same Provisioning workflow). I guess the other intervention is when we decide to change the configs (like number of queues) and trigger a re-deploy. But thats about it. So far, we have spent a very small percentage of our support budget for this.
- deleted 2y ago[deleted]