Nopcommerce: MongoDB database support

[AndreiMaz]

Similar to https://github.com/nopSolutions/nopCommerce/issues/415

[atulrungta]

Hey @AndreiMaz ,

Have your team made any progress so far on this feature? Unfortunately, two of my large sized customers went on hold when I told them that nopCommerce 4.30 will have MongoDB support for sure LOL..

I am asking this because I didn't saw any commits regarding it in last 10 days :)

[AndreiMaz]

@atulrungta Currently we're working on https://github.com/nopSolutions/nopCommerce/issues/239. Then we'll start working on other tasks

[atulrungta]

Hello @AndreiMaz ,

Are you still planning to provide this feature in current road-map?

[AndreiMaz]

@atulrungta yes

[atulrungta]

So, will you work on this feature once moving away from EF is done? I really wish to see 4.30 as a stable version with MongoDB. Almost 4 big sized projects are on hold :)
@AndreiMaz

[jabberdeepa]

So, will you work on this feature once moving away from EF is done? I really wish to see 4.30 as a stable version with MongoDB.

@atulrungta have you try GrandNode project?

[atulrungta]

So, will you work on this feature once moving away from EF is done? I really wish to see 4.30 as a stable version with MongoDB.

@atulrungta have you try GrandNode project?

Yes. We worked on GrandNode for few projects in past. It is very unstable.
I strongly never recommend GrandNode unless insisted by customers :)

[atulrungta]

@AndreiMaz have you really removed this feature from 4.30 milestone?
It means, we won't see MongoDB support in this version?

[AndreiMaz]

@atulrungta After moving away from EF in this version, we can implement MongoDB quite fast. But we don't want to postpone this release. That's why it'll be implemented in 4.40. Good news is that we decided to set the release cycles again back to 6 months

[atulrungta]

@atulrungta After moving away from EF in this version, we can implement MongoDB quite fast. But we don't want to postpone this release. That's why it'll be implemented in 4.40. Good news is that we decided to set the release cycles again back to 6 months

Hmm.. it means we have to wait for another 7 months to see MongoDB. It was most awaited thing for me in this version but yeah, good things are happening :)

[KrzysztofPajak]

@atulrungta
Could you explain what is unstable?

[KrzysztofPajak]

@AndreiMaz
As we talked in june, I don't think it is possible to move to MongoDB.
There is a lot of difference between nosql vs sql database.
But we will see :)
I think the NopCommerce team should focus on integration with Elasticsearch

[atulrungta]

@atulrungta
Could you explain what is unstable?

Are you talking about GrandNode? Their code have a lot of bugs as per last time I checked around a year back.
Their implementation of MongoDB is also slower than expected as per our load tests at that time.
The website was going back and forth on almost all of deployments we did. We fixed that with certain code changes regarding MongoDB at that time.
Although it is on .net core completely but it was still referring to .net framework at that time.
I don't know whether they have improved now, but my past experience is certainly not good enough to suggest any of my customers to use it.

[atulrungta]

Hey @AndreiMaz ,

Is this in progress? Can we expect to see this in 4.40?

[AndreiMaz]

@atulrungta Right, we plan to implement it in 4.40

[poyker]

Hi guys,

What is the point of adding yet another DB support?
Will nopCommerce users benefit from using MongoDB and what these benefits will be?

[xcellenceit]

Hi guys,

What is the point of adding yet another DB support?
Will nopCommerce users benefit from using MongoDB and what these benefits will be?

I think you're raising valid point here.

[AndreiMaz]

@poyker Increase our customer base and popularity by giving more choices to our users. Also we think that it can significantly increase the performance compared to other databases (we'll check it very-very soon)

[mi-sohel]

@AndreiMaz thanks. Yes, it will help significantly increase performance. Is there any update on it?