david-j-vujic

For Python, I would recommend to try keeping the balance between Functional and Pythonic.

An example: a comprehension is often a better idea from a “Pythonic” perspective than using the map function.

FastAPI is a good choice for developing Python APIs. It has a modern feel to it, and is easy to learn. When I think about it, I could say the same things about Polylith.

Some have already mentioned Polylith, but what might not be known is that it is available for Python too (I’m the maintainer of the Python tooling).

What is mentioned in the article reminds of the Polylith Architecture, even if Polylith probably has a more simplistic view on code: a flat structure, made of something called “bricks” - that are small namespace packages. These ones are combined into features, the features are combined into apps or services.

You can choose how to deploy your artifacts - as a single Monolith, or several microservices. Since the code is not coupled to the built artifact, it isn’t a big thing to change it from one type to another.

Docs here if you want to know more: https://davidvujic.github.io/python-polylith-docs/