When building a FastAPI project with PostgreSQL, you need a reliable way to manage your database schema over time. As your application evolves, simple table creation is not enough. You need a way to safely apply, track, and roll back changes.
Alembic provides a structured, version-controlled approach to database migrations. In this guide, weโll walk through how to set up Alembic with FastAPI, SQLModel, and PostgreSQL, including common issues youโll run into when working with Docker.
Choosing the right database can make or break your application. It affects how your data is stored, how fast your app runs, how easily it scales, and how quickly your team can develop features. Two of the most popular optionsโMongoDB and PostgreSQLโoffer very different strengths. At Keyhole Software, we help businesses make smart technical decisions based on their specific needs. …
Your PostgreSQL database might be handling todayโs workload just fine, but what happens when traffic surges, data volume skyrockets, or queries start taking longer than expected? Without the right scaling strategies, performance bottlenecks can creep in, leading to slow response times, reliability issues, and frustrated users. In this guide, weโll break down the best practices for scaling PostgreSQL, ensuring your …
The database you choose plays a critical role in the way your application performs, scales, and handles data over time. Two of the most popular open-source relational databases are PostgreSQL and MySQL. While they share some similarities, they also have key differences that could significantly impact your project. In this article, we’ll break down the essential factors to consider when …
Every long-term project will outlive at least some of the technologies it was originally built with. For example, a project I have been involved with recently ran into this situation. The app is hosted on Heroku, and over the years, the available MongoDB add-ons have changed and dwindled until now, there is only one.
Several migrations between MongoDB add-ons have already happened because of shutdowns. So, it was decided that rather than migrating to the last one still in existence, the project would switch to using PostgreSQL, which is supported directly by the Heroku team.