3 ms·
If you do that your testing and deployment stacks remain monolithic, running tests / deploying becomes increasingly slower and more expensive. With a lot of dev
by bpicolo 10y ago
If you do that your testing and deployment stacks remain monolithic, running tests / deploying becomes increasingly slower and more expensive. With a lot of developers on a big app and good CI practices a company might spend hundreds/thousands of compute dollars a day just running tests for one monolithic app.
- eropple 10y agoWhy does one imply the other? I regularly build applications out of composable libraries that are wired together with bog-standard dependency injection systems and each separate library handles its own testing and can be kicked off in its own CI process. (I could even add in the boilerplate and performance hit of microservices, if I wanted to--just launch each library with its own thin HTTP layer. But I don't and don't need to.)