Could you describe how development workflow could look like

[pie6k]

in other words:

what is recommended and the fastest possible way to have changes applied after every CMD + S in code editor?

Note with things like React hot-reloading it's like 0.5s between CMD + S and change being visible in the browser.

[marvincaspar]

One additional question: Is this example realistic? Should all microservices have these small size or would you create microservices with more features? I mean user-api and auth-api could be merged into one service because it is all about user handling.

[elgris]

@pie6k one of the ways would be running all the APIs on our local, outside of Docker, so there is no need to rebuild docker images each time. In order to do that you need to follow READMEs provided for each API.

@mc388 Ideally, I'd build a service per business domain, splitting further if needed (in 95% cases it's not needed). In this case, you're right, users-api and auth-api should be reworked.This exercise is definitely an example of overengineering which has different primary goal: to have a very simple polyglot environment for integration experiments. For instance: "if I integrate distributed tracing into this, how many bugs I'll get?". It helped to find a plenty of problems (with another tracer, though).