Repository navigation
Who uses MikroORM in production? #296
Description
Hi there, I am currently evaluating a bunch of orm-a-like libraries for an upcoming project.
I have experience with sequelize and waterline. I found mikro-orm while trying to choose a new ORM for a company I work for. I noticed there are not a ton of stars or used by stats quite yet on this project, but after reading through the docs, I think it has great potential.
It deserves more traction and I am asking myself - why is mikro-orm not more popular? And who is actually using it in production?
I know it sounds stupid, but is there some who-uses-it listing I can show to an IT decision maker?
Nevertheless, you did an awesome job and built a great library!
P.S.-- I stole the outline of this comment from Vincit/objection.js#1069.
Activity
B4nan commentedon Jan 9, 2020
Hello there and thanks! Unfortunately there is no list of users/companies, obviously I know about few people using it (starting with myself :]). Let's keep this open and pinned to the top, hopefully we will get some feedback here.
About the "low" popularity, I think I am the one to blame - I love programming, much more than writing (and if I do write, I usually write the docs instead of articles). There are very little articles about MikroORM and those that I wrote did not get much traction. Unfortunately I have very weak (and not very programming oriented) audience on social networks, so it is hard for me to promote it properly.
Regarding articles, I picked medium.com as the platform of choice, but I have seen pretty negative feedback in general to medium during last few months, so I am considering to go with dev.to as the main platform (reposting it to medium too). I do have simple blog now on the website as well, but there are no comments and reactions available, so I think dev.to will be better choice. Another problem I had was with Daily.JS, I had to ask multiple times to promote the article (share on their behalf) on their twitter account. Maybe another publisher would suite better.
I hope the v3 release will get more traction and things will start moving more rapidly. I spend last 2 weeks vacationing, but I'd like to finalize the release article soon and get it out finally.
Btw keep in mind that this project is still relatively young, I "went public" with it with v2 in 04/2019. And you know, it's just another ORM in the JS world :]
jeffbum commentedon Jan 10, 2020
@B4nan Thanks for replying! I have been researching ORM's for Node this past week, and am really intrigued with Mikro-orm. I'm presenting it as an option for my company.
lookfirst commentedon Jan 15, 2020
@jeffbum You don't know me, but trust me, go with Mikro.
As @B4nan says, it is just a popularity contest. Mikro is pretty new, v3 is definitely new, but the code is excellent and Martin is totally wonderful to work with. This is by far the best ORM for JS/TS on the market. The rest do not even compare.
jeffbum commentedon Jan 17, 2020
@lookfirst I appreciate the recommendation. At the moment, chose another direction, but I am quietly duplicating efforts in Mikro to be able to compare side-by-side with the other orm. Just in case I want to make a mid-game switch ;)
lookfirst commentedon Jan 18, 2020
@jeffbum Interesting feedback for sure! Can we expand on that? Would be good to know your thoughts. Your thoughts are appreciated because I think it would help others make their decisions as well as help this project in marketing.
Maybe others have questions for you as well...
ujwal-setlur commentedon Jan 28, 2020
I am doing the same research for my project, and was considering prisma2, when I ran across Mikro-ORM in a medium article. Looks very very intriguing, so I guess I am going to dig more.
lookfirst commentedon Jan 28, 2020
For me, one primary thing I deem absolutely necessary with working with sql databases, is strong transactional support. Just searching the respective repositories should give you a hint about which one to go with... Mikro ORM vs. Prisma2
doublemcz commentedon Jan 30, 2020
I use this ORM in 3 apps and so far I must say, it is brilliant. The simple usage of MikroORM is really nice. I switched to this because TypeORM and Typegoose have really bad UX.
I use this FW as follows at this moment:
Martin
Kudos to @B4nan. Once I am in Prague, will pay you some nice and delicious pizza or burger.
RDeluxe commentedon Apr 21, 2020
We started using Mikro for our projects, and we plan to continue in the future. Great work, we are spreading the word !
CosmeLorim commentedon May 10, 2020
I am using it in one project and a co-worker is using it in two more projects by my recommendation, all in a serverless environment.
Using mikro-orm has been very productive!
jasonpincin commentedon Jun 13, 2020
Hello! This is not a feature request, but rather feedback, since this issue seems to be seeking it.
I'm evaluating "light" ORMs for a big project and mikro-orm looks fantastic. The one likely blocker for me choosing it is the seeming inability to have multiple database connections (correct me if I'm wrong). For this project, we aim to expose the ability for subsystems/models to choose from one of several persistence layers, and as such need the ability to dictate which layer a model is backed by.
Typeorm supports this via:
@Entity({ database: "dbName" })Unfortunately, no matter what ORM I choose I need to implement a custom driver for one of our stores, and the path to accomplishing that is not nearly as clear in Typeorm as it is in Mikro-orm, so I'm still at a cross-roads on my evaluation. I'd like to offer our contributors a consistent modeling language without having to be concerned with all the details, but easier said than done.
Regardless, great work going on here! I will certainly be watching this project 👍
41 remaining items
mandarzope commentedon Jun 2, 2024
@medusajs has migrated to mikro-orm. They are a VC funded company. @B4nan I am hope this would bring more attention to mikro-orm and more sponsorship.
B4nan commentedon Jun 2, 2024
Since you are bringing this topic up, let me say that the situation with sponsors is not great.
First, let me start with the good news. One great thing that happened in February this year - I got in touch with CDN77, and they offered to sponsor my work on the ORM. We agreed on a direct contract, so you won't see them in my GH sponsors profile, but their contribution is significant, similar to all the other sponsors combined.
But this brings me to the darker side of things, which is GH sponsors. Over the past 12 months, the numbers were stagnating, if not declining. When I check the activity in 2024, I can see the following:
So a few one-time donations, almost no new monthly sponsors, and a lot of cancellations of monthly donations. At the same time, I can surely feel the increased attention, since there is a bigger demand for support (the number of purely support issues/discussions is growing, same with people on discord).
I am grateful for all the contributions, but if there wouldn't be the one from CDN77, the numbers would end up much worse than the year before. I don't have any other income for this adventure outside of the contract with CDN77 and the GH sponsors, yet it takes more and more of my time.
Please consider sponsoring my work on the ORM, or even better, try to convince the company you work with to do so.
Let's try to make this project sustainable. Thank you!
v1d3rm3 commentedon Jul 2, 2024
Support on MSSQL brought me here. I've started my contributions.
LeulAria commentedon Jul 19, 2024
@B4nan great orm, will try to contribute on creating some MikroORM Studio like the other ORM's and nice landing page
some time :)
conoremclaughlin commentedon Jul 20, 2024
Sponsored! @B4nan with Nest.js now moving to first-class support of MikroORM, and the future of TypeORM clearly uncertain, maybe to drum up more support, you could convert the README to highlight your current sponsors along with tiers? That way those sponsoring get exposure, and people can gain confidence and / or recognize more may be needed. It's a common pattern for OSS projects, including Nest, Drizzle, TypeORM, and many others. Seems to be worth a shot.
Perhaps also a rebranding to the "Mikro Team", and that team is currently recruiting (apply through this form here, etc.) would also help the conversion from this being a one-man show to a team-supported effort and perhaps even a company one day ala. Vercel, Apollo, etc.
It definitely feels like anyone considering an ORM right now is going to be closely looking at Prisma, MikroORM, Drizzle, or Sequelize (if fearful). Feels like a good time to strike.
You also mentioned on Reddit potentially integrating Kysely, and gaining further type safety for the query builder would be another way to build momentum. This also helps Kysely after Drizzle ate a bit of their lunch. It could also lead to a mutually beneficial collaboration and partnership. Put a light theme on Docasaurus and change some of the standard fonts and you're halfway there to your own startup!
Thanks again for your hard work! 38 issues for MikroORM vs 2,400 for TypeORM shows your absolute dedication.
dani-filipovic commentedon Aug 2, 2024
Hey @conoremclaughlin ,
what does this mean? Is there a
@nestjs/mikro-ormpackage in the works? If so, this is great news, but I haven't been able to find any news regarding MikroORM and NestJS support moving to "first class". What is your source on this?Thanks!
boenrobot commentedon Aug 2, 2024
@dani-filipovic
It's the other way around...
@mikro-orm/nestjs
It has existed for a long while.
giancarlo-dm commentedon Aug 21, 2024
@dani-filipovic I particularly don't use the "official" nestjs <> mikroorm package integration. I found some limitations and I required more control over the DB connections and Async Local Storage integration. So I ended up creating my own provider + EntityManager middleware to
.forkthe EM for every request. Since I have full control, I added a couple of checks (such as dangling transactions when a request ends) and added a@Transactionaldecorator (used on service methods) to automatically manage cross service transactions without needing to manually callem.being(),em.rollback()andem.commit().vroudge commentedon Sep 11, 2024
Hey there!
We're Cinqo a new player in the industrial waste recycling space and we're totally LOVING mikro-orm. @B4nan support is absolutely excellent and the list of issues on the ORM should be a subject of immense pride.
It flawlessly works in production right now.
AmeroHan commentedon Jul 13, 2025
@nichenqin Noting that undb is no longer using MikroORM but has switched to Drizzle, could you explain the motivation for this?
knocte commentedon Feb 2, 2026
Hello folks. I'm interested in adopting MikroORM because I have the need to migrate the data of a project from MongoDB (Mongoose) to PostgreSQL. Anyone did such a similar migration before? Is it recommended? Thanks!
darkbasic commentedon Feb 2, 2026
NoSQL is a completely different beast from a relational database: an ORM won't abstract all these differences away.
B4nan commentedon Feb 2, 2026
On the other hand, it is doable, and having an ORM that supports both will help a lot. I actually did this conversion myself in the early days of MikroORM, moving from mongo to postgres. The main gotcha is the PKs/FKs, since you can't use objectid in postgres. You will need to generate conversion scripts (and be prepared for downtime). It's a tricky thing to do, if you want to discuss that, let's open a new discussion instead of spamming dozens of people in this issue.
varshithmee commentedon Mar 25, 2026
We are PredicTx Health and we use MikroORM in our codebase and hopefully get into production within the next couple of months! We are bringing precision medicine to every doctor's workflows!
andres-dejesus commentedon Jul 28, 2026
I'm using it in production for Cursilo, along with Nextjs and Supabase.