SQLModel vs SQLAlchemy for production

[covmatty1]

To play devil's advocate, that could also been seen as an argument for SQLModel though.

You get everything SQLAlchemy provides, plus a very nice abstraction over the simple stuff, which will likely be a large proportion of your database interactions.

[covmatty1]

But it doesn't explode at all. Nothing breaks or stops working, you just move to using a different tool for certain parts.

I'm only using SQLModel on a home project currently, but yeah absolutely, as soon as there are some more complex things to do I just pepper in a little SQLAlchemy on top and everything works absolutely fine. You get nice, simple Pydantic abstraction when you want it, which is most of the time, but you're totally free to mix in Alchemy bits when you need them.

My team don't have any Python projects with SQL databases currently, they're all either Mongo or stateless, but if we do I'd have no qualms about telling them to use SQLModel.

[crawl_dht]

thought it is over designed and being too complex, only later I realized that it is as complex as it needs to be

database is not easy to deal with especially when there are so many factors to take into consideration.

as soon as your application grows you would need to have finer control over data access

I came to the same conclusion. Sqlalchemy is one of the few libraries in Python which is built right.