Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to MongoDB 4.0 #269

Closed
klaussner opened this issue Feb 16, 2018 · 6 comments
Closed

Upgrade to MongoDB 4.0 #269

klaussner opened this issue Feb 16, 2018 · 6 comments

Comments

@klaussner
Copy link
Member

@klaussner klaussner commented Feb 16, 2018

The main feature of MongoDB 4.0 (scheduled to release next summer) will be multi-document ACID transactions: https://www.mongodb.com/transactions.

@mitar
Copy link

@mitar mitar commented Nov 9, 2018

So what is the process here? MongoDB4 4.0 is supported, but transactions are not yet, no?

@klaussner
Copy link
Member Author

@klaussner klaussner commented Nov 17, 2018

MongoDB 4.0 is supported in Meteor 1.8 but transactions are not (yet) part of the Minimongo API (related FR: #311). 🙂

@klaussner klaussner closed this Nov 17, 2018
@mitar
Copy link

@mitar mitar commented Nov 18, 2018

Minimongo API? You mean server-side MongoDB API.

@mitar
Copy link

@mitar mitar commented Nov 18, 2018

But you are right that it would be in fact interesting to have transactions also in Minimongo. This could allow one to prepare multiple changes to documents without reactivity triggering and then commit and re-render at once.

@klaussner
Copy link
Member Author

@klaussner klaussner commented Nov 27, 2018

Yeah, I meant both. 😄 I think it would be good to keep the API as isomorphic as possible.

@a4xrbj1
Copy link

@a4xrbj1 a4xrbj1 commented Jan 11, 2019

So what's the latest on this one? This isn't encouraging news

MongoDB 4.0 is supported in Meteor 1.8 but transactions are not (yet) part of the Minimongo API (related FR: #311)

It goes along the same line of what I wrote in the State of Javascript thread. I don't get the feeling that MDG is supporting Meteor enough, in the way that too much focus (meaning manpower) is on GraphQL development and important features (that would make Meteor way more attractive to most serious developers) like the above multiple ACID transactions features isn't implemented.

That leads to small Startups and companies giving up their hope for Meteor. At least that's how my employees and me see it.

MongoDb makes big steps forward (like everyone agrees to in the announcement of MongoDb 4 thread) but Meteor is further falling behind and no clear timeline or commitment to implement this feature is given by MDG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants