3 ms·
Mountebank/mocking is a great solution when your components are too big to spin up new ones for 'free'. It's exactly because Docker-based components end up so
by tekacs 12y ago
Mountebank/mocking is a great solution when your components are too big to spin up new ones for 'free'.
It's exactly because Docker-based components end up so big that it seems hard to believe in the viability of that approach to microservices though. :/
It's a great stopgap/migratory step, though.
- bbyars 12y agoI think some level of integration testing is always a good thing, but spinning up all dependent services just so you can test yours leads to all kinds of problems, even in microservices. You end up with cascading dependencies. At scale, some level of stubbing is required to test.
- tekacs 12y agoAgreed. We _partially_ solve this problem by letting you run a dev cluster that you can use for services which are awkward to run locally, but stubbing/mocking definitely has a place in automated testing, certainly.