Monolithic Applications and Microservices

The most important idea is the concept of separating concerns: Different responsibilities should be distributed across diverse components. Just as in our code (a more detailed level of design) it wouldn't be good to have a giant object that knows everything, in our architecture, there shouldn't be a single component owning everything.

Different components vs. different services

There is, however, an important distinction. Different components don't necessarily mean different services. It's possible to divide the application into smaller Python packages and create a single service composed of many dependencies.