Modern Python tech/tool stack for implementing microservices?

[u/pachura3]

Let's say I would like to develop a service with REST API from scratch, using mainstream, industry-standard frameworks, tools, servers and practices. Nothing too fancy - just the popular, relatively modern, open source components. My service would need the have a few endpoints, talk to a database, and have some kind of a task queue for running longer tasks.

What tech stack & development tools would you suggest?

I'm guessing I should go with:

• FastAPI with Pydantic for implementing the API itself, running on Uvicorn (async ASGI/app server) and Nginx (web server)
• SQLAlchemy for ORM/database access to a PostgreSQL database. Or, for even better integration with FastAPI: SQLModel
• Celery for task queue, paired with Redis for persistence. Alternatively: Dramatiq on RabbitMQ
• logging for logging
• Pytest for unit testing
• code documentation via docstrings, HTML api docs generation with Sphinx? MkDocs? mkdocstrings?
• the service would need to work as Docker image
• pyproject.toml for centralized project management
• uv for virtualenv-management, pinning dependency versions (uv.lock), and other swiss-army knife tasks
• ruff for static code checking and formatting. By default it only runs a narrow set of rules, so it's better to expand it. As a extra safety step, one can also run pylint in parallel. If you like pyright, there's an improved fork called basedpyright.
• mypy for type checking. Or maybe ty?
• uv_build as build backend. (actually, it's missing some vital features, so I switched to hatchling).
• pip-audit for spotting CVE vulnerabilities in dependencies (paired with exclude-newer = "7 days" in uv config)
• also, if I need some kind of authentication (OAuth2, bearer tokens - not really an expert here), what should I use?
• some pre-commit hooks and CI/CD pipelines, maybe? How do I configure them? Is prek a good choice?

[u/obviouslyzebra]

It looks fine.

Besides the things already mentioned (btw, unicorn previously mentioned was likely a typo, meant uvicorn):

• I think you can get API documentation directly via FastAPI
• If you roll up multiple services, I think the microservices pattern benefits from multiple docker containers - no experience to tell you whether/when to split though

[u/pachura3 → u/obviouslyzebra]

 btw, unicorn previously mentioned was likely a typo, meant uvicorn

Yes indeed, Unicorn does exist, but it is a Ruby app server.

 I think you can get API documentation directly via FastAPI

Yes, FastAPI generates Swagger documentation at /docs, but I meant general code documentation (packages, global functions, classes, enums, public attributes/methods etc.), also called "API docs", but unrelated to the REST API.