I’m a beginner and I want to work on a project with FastAPI. I’m not sure whether to use Motor or Beanie ORM because I don’t see the benefits of Beanie over Motor. I’d like to know your opinion on whether it’s worth using Beanie.
I have worked with both Motor and Beanie & honestly, it really comes down to what kind of experience you are looking for as a developer.
Motor is awesome if you are comfortable handling things manually, it is low-level, gives you full control & is great for custom queries. But that also means more code, more boilerplate & you will be doing a lot of the heavy lifting yourself like data validation, structure, etc.
Beanie builds on top of Motor & gives you a smoother, more Pythonic experience with Pydantic models and a structure that plays super well with FastAPI. If you are still learning or want to move fast without worrying about the tiny details. Beanie can save a lot of time and frustration. It’s also great for cleaner code and easier onboarding if you are collaborating later.
1 Like
Thank you for your response. I think I’ll go with Beanie. Just to make sure I understand correctly. When you mention validation, do you mean that Beanie validates the data before sending it to the database? For example, with just Motor, even if FastAPI validates the request body or parameters, there’s no guarantee that the data we actually send to the database is correct. Especially if something gets added or removed between receiving the request and writing to the DB. Is that what you meant?
1 Like