3 ms·
Even in parallel, there are tradeoffs: run them all in one container, or chunk them out to available workers. The first runs into resource constraints; the latt
by turtleyacht 2y ago
Even in parallel, there are tradeoffs: run them all in one container, or chunk them out to available workers. The first runs into resource constraints; the latter takes up everything in the shared pool.
With IaC, emulating a constellation of all dependent services along with the site is technically feasible. (There are other possible constraints.)
What's your ideal scenario? For example, k8s + cloud, ephemeral db, auto-merged IaC file of a thousand services, push-button perf testing, regression suite with a hundred bots, etc.
- arkh 2y ago> What's your ideal scenario? On premise k8s cloud where you can deploy many instances of the exact same services you have in prod. Let's say a E2E test takes 5s to run, your deployment takes 2mn and you want to stay under the 5mn line for running your test suite: deploy an instance of all your services and their databases per batch of 30 tests. I can understand this not really being possible at an Amazon scale. But for most businesses? A good beefy server should be enough.