2

A NoSQL database to meet the challenges of storing larger catalogues of data, this scalable solution will bring unmatched performance. But as we know , Magento has a large number of tables and those tables have relationships to each other. So we will not be able to completely migrate in one go.

But we can be migrate few modules which make sense to do so? What are the modules that can be migrated or is there any other way that a NoSql database like MongoDB can be used.

I have also read how to connect to MongoDB, but need to know which modules which will increase performance.

Improve this question
5
  • good question @sunel.+1 for for you
    – Amit Bera ♦
    Commented Jan 12, 2015 at 7:15
  • 1
    mongogento ecommerce-performances.com/en/mongogento.php
    – s_h
    Commented Jan 12, 2015 at 9:40
  • but that only has product module to mongodb and also it still uses sql behind the scene . what are the other modules that can be migrated and also fully to mongodb
    – sunel
    Commented Jan 12, 2015 at 9:48
  • @Marius that is not relevant question and mine is entirely different pls verify and remove duplication
    – sunel
    Commented Jan 12, 2015 at 9:50
  • I think the biggest performance issue is the catalog - if you move these information to MongoDB or ElasticSearch, you will increase the performance. We use ElasticSearch for Searching and LayeredNavigation in some projects - all other product data will stay in mySQL to avoid conflicts and have less work.
    – Matthias Kleine
    Commented Feb 13, 2015 at 19:38

1 Answer 1

Reset to default
3

Interesting question. Im not sure ALL of Magento would suite a NoSQL style database storage. I can see how using MongoDB, ElasticSearch etc for Products makes sense as its document storage. So different products could contain different types of data to make up a valid product. However for more structure data such as configuration navigation categories I think a relational MySQL database is the better fit.

the problem this creates is that it is very expensive to then open 2 database connections as well as not being able to JOIN on the data sets to link data. Relationships in Mongo ( it doesnt really have them ) is not fun. Neo4J is a graph DB that supports relationships but again core_resource and the category structure I would see little value being in a Document store.

If I had to move modules out from MySQL initial ideas would be:

  • Search
  • Products
  • Invoices / Orders
  • Customers

To me these are the modules that store data that would benefit from these NoSQL schemaless styles. Products that are represented by physical document's in the world A4 product sheets that can vary by category manufacturer would be ideal.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.