Native vs container mode
Each micro in a scenario runs in one of two execution modes, and you choose it per micro:
| Mode | What it is | When |
|---|---|---|
| native | The micro starts as a process on your machine (with Maven, npm, uvicorn…) | The micro you’re working on: fast start, hot reload, easy debugging |
| container | The micro starts inside a Docker container | Background micros: isolated, reproducible environment, without cluttering your machine |
The usual combination is mixed: native for the one you develop, container for the ones you just need running for the flow to work.
Changing the mode
Section titled “Changing the mode”In the scenario’s Cards or Table views, each micro has a native/container toggle. You can also set a micro’s default mode in its editor (Micros section).
Container mode requires Docker to be started. Native mode uses the repo’s wrapper
(mvnw, .venv) or the binary on your PATH; MicroLab does not install toolchains for
you.
Customizing native startup
Section titled “Customizing native startup”Native-mode startup can be fine-tuned per micro (properties, arguments, database, command…) without touching the repo. See Customize startup.