Python/FastAPI Multi-Tenant Backend Enhancements
Publicada el 2026-08-02
Descripción de la oferta
My SaaS platform already runs on FastAPI with SQLAlchemy 2.0, Alembic, and Postgres. The foundations are solid, yet several partially built features still need to reach production-ready quality, and each change must respect strict multi-tenant data isolation. MORE DETAILS TO BE DISCUSSED AND SHARED Scope • Finish the outstanding endpoints and background jobs that were started but never wired end-to-end. • Keep every migration in sync through Alembic and validate that tenant-level schemas remain untouched by other tenants’ data. • Refactor any SQLAlchemy 1.x patterns that may still linger so we are fully 2.0-compliant. • Add the missing unit and integration tests (pytest) to confirm isolation, correctness, and performance before release. Acceptance Criteria 1. All new or completed endpoints pass automated tests for at least two tenant IDs in parallel. 2. Alembic upgrade/downgrade commands run cleanly on an empty database and on a live copy. 3. SQLAlchemy warnings are reduced to zero, and only 2.0-style ORM or Core syntax is present. 4. Post-merge CI shows green for linting (ruff/black), typing (mypy), and tests (coverage ≥ 90 %). You’ll push changes to a GitHub repo with an existing CI pipeline; I’ll review via pull requests and release in staged environments. Clear, well-commented code and concise commit messages are essential so I can track what changed. If this matches your expertise, let’s get started—once these features ship, the product can finally scale to new customers confidently.
Skills
Fuente original: freelancer