Explore >> Select a destination
|
You are here 
|
avelino.run | ||
| | | | |
philiplaine.com
|
|
| | | | | Three years ago, I was part of a team responsible for developing and maintaining Kubernetes clusters for end user customers. A main source for downtime in customer environments occurred when image registries went down. The traditional way to solve this problem is to set up a stateful mirror, however we had to work within customer budget and time constraints which did not allow it. During a Black Friday, we started getting hit with a ton of traffic while GitHub container registries were down. This limited our ability to scale up the cluster as we depended on critical images from that registry. After this incident, I started thinking about a better way to avoid these scalability issues. A solution that did not need a stateful component and required minimal operational oversight. This is where the idea for Spegel came from. | |
| | | | |
paramdeo.com
|
|
| | | | | ||
| | | | |
blog.martinig.ch
|
|
| | | | | Informations and opinions about software architecture, developers on call, holacracy, Scrum, continuous testing, product management, saying thank you, tech leadership, customer journey maps, code reviews, code sharing, good bugs, android testing and open source project management. | |
| | | | |
vitalyobukhov.wordpress.com
|
|
| | | Visit the post for more. | ||
