Difference between revisions of "Testing Microservices"
From CitconWiki
Jump to navigationJump to search| Line 3: | Line 3: | ||
* NOC (Network Ops Center) - | * NOC (Network Ops Center) - | ||
* New bank - common stack, clojure, AWS | * New bank - common stack, clojure, AWS | ||
| − | * Netflix also started with same stack, but it diverged assuming | + | * Netflix also started with same stack, but it diverged assuming commonality of contracts. But Netflix has fantastic monitoring practices |
| + | * Challenge - in a micro-services environment, how do you catch issues before production if all tests were fine for individual environments? | ||
| + | * Heavy Monitoring | ||
| + | * Learning the process for a year before automating it was helpful (some automations are not needed) | ||
| + | * Disney provides client libraries. Versioning - providing min and max. Netflix - started with that, had to stop cause there was too many different libraries. | ||
| + | * Sometimes new practices require change in culture. | ||
| + | * Deploying across different geographic zones has to be staggered - deploy to EU, wait for 6 hours, confirm it works, deploy to next region | ||
Revision as of 12:38, 4 February 2023
Tools
- Splunk stack and hashi wrapper for monitoring
- NOC (Network Ops Center) -
- New bank - common stack, clojure, AWS
- Netflix also started with same stack, but it diverged assuming commonality of contracts. But Netflix has fantastic monitoring practices
- Challenge - in a micro-services environment, how do you catch issues before production if all tests were fine for individual environments?
- Heavy Monitoring
- Learning the process for a year before automating it was helpful (some automations are not needed)
- Disney provides client libraries. Versioning - providing min and max. Netflix - started with that, had to stop cause there was too many different libraries.
- Sometimes new practices require change in culture.
- Deploying across different geographic zones has to be staggered - deploy to EU, wait for 6 hours, confirm it works, deploy to next region
