3 ms·
In an ideal world, pushing new features would have no impact on stable mature features like browsing files, comment threads, etc
by xkcd-sucks 7y ago
In an ideal world, pushing new features would have no impact on stable mature features like browsing files, comment threads, etc
- leetrout 7y agoThat’s part of the micro service promised land, right?
- cranekam 7y agoNo, I think it's more part of how to run a complex system with a lot of people changing stuff at once. Having good monitoring, kill switches, staged rollout, continuous deployment, and so on are all things that contribute more making a reliable service than how microserviced it is.
- duxup 7y agoIdeal I agree ... and yet the real world is exactly the opposite ;)
- grogenaut 7y agoInternal to Amazon we consider that about 80% of issues/outages/etc are due to changes. This may sound "duh" but this is over 10k plus investigations. Much if the work is just minimizing the impact of this changes by finding them before customers do. This includes things like unit, integration testing, canaries, cellular/ zonal / regional deploys, auto rollbacks, multi-hour bakes, auto load tests, and much much monitoring. Not to mention cross team code reviews, game days, ops reviews.
- lovegoblin 7y agoWhich world is that?
- fastball 7y agoToo bad this is the real world.