4 ms·
It seems like their initial problems were: 1. Tests hitting 3rd party APIs are flakey & slow 2. The job queuing mechanism can cause all jobs to be slowed by a
by sequoia 8y ago
It seems like their initial problems were:
1. Tests hitting 3rd party APIs are flakey & slow
2. The job queuing mechanism can cause all jobs to be slowed by a single 3rd party API outage/slowdown
Eventually they arrived at:
1. Replay responses to speed up HTTP based tests
2. Create a smarter queuing mechanism in house
I'm not sure what microservices has to do with any of this. Anyway, kudos to them for having the courage openness to share their learning from mistakes!