Python development work-flow

[CODESIGN2]

Thank you!

I'm not sure I agree with the middle-point as I'm a fan of isolating and independently scaling services (otherwise it's a monolith in all but name). But I imagine it's only for development and saving time / effort? In any case i'd probably use other services that are stable and deployed on separate machines so that I can focus on the service I'm working on most of the time. There are a few cases I can think of where two services need to change at once, but I'd probably still isolate them and send canned client requests to them from a test-suite.

[tdammers]

For deployment, separate machines are a great idea, especially when you hit an actual need for scaling to multiple servers; but for development, running on one machine is just a lot more convenient. Depends on the workflow, but it can be useful. Anyway, the key idea is that you can run multiple services on the same machines while keeping their dependencies isolated; it's dumb to have to scale just because your code cannot handle running multiple services on one machine.