clustering AEM 6.0 Sharding with (Mongo DB Router, Primary and Secondary) | Community
Skip to main content
Chandra_gupta
Chandra_gupta
New Participant
October 16, 2015
Solved

clustering AEM 6.0 Sharding with (Mongo DB Router, Primary and Secondary)

  • October 16, 2015
  • 3 replies
  • 1208 views

I am referencing this document http://adobedocsdiff.headwire.com/sitediff/serve/2015-01-29/data/docs/en/aem/6-0/deploy/recommended-deploys.html for  Oak Cluster with Sharded MongoDB.

Let me ask few questions.

Question1. Can we have Router/Mongos and one of MongoDB Primary Server on Same box where AEM Publish is installed considering box is very high capacity in terms memory and CPU.

Question2.  Mongos/Router i believe is very lightweight not actual Database store like Mongo DB primary or secondary?

Question3. if we install AEM with MongoMK with no clustering just like AEM with TarMK..Can we apply clustering in future on Mongo DB to leverage replication feature of MongoDB?

Regards,
Chandra

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

Questions 1 and 2 are primariy mongoDB related and are not specific to AEM; you could also check the generic MongoDB documentation for these questions.

To 1/2) a router isn't a heavyweight process in terms of CPU or RAM. So from my point of view they can be deployed next to a MongoDB instance.

To 3) You don't need to use clustering, when you use MongoDB, but it's quite natural to do so. But there's a (huge?) performance difference between AEM on MongoDB and AEM on TarMK. And you will have the possibility to migrate from TarMK to MongoDB. So you can start on TarMK and switch to MongoDB if you need clustering.

kind regards,
Jörg

3 replies

joerghoh
joerghohAccepted solution
Employee
October 16, 2015

Hi,

Questions 1 and 2 are primariy mongoDB related and are not specific to AEM; you could also check the generic MongoDB documentation for these questions.

To 1/2) a router isn't a heavyweight process in terms of CPU or RAM. So from my point of view they can be deployed next to a MongoDB instance.

To 3) You don't need to use clustering, when you use MongoDB, but it's quite natural to do so. But there's a (huge?) performance difference between AEM on MongoDB and AEM on TarMK. And you will have the possibility to migrate from TarMK to MongoDB. So you can start on TarMK and switch to MongoDB if you need clustering.

kind regards,
Jörg

Chandra_gupta
Chandra_guptaAuthor
New Participant
October 16, 2015

Okay, for point 3.

Purpose behind using MongoMK with AEM 6 standalone not clustering is to avoid migration from TarMK to MongoMK in future when clustering will be covered/required. I believe migration is little bigger effort.

When you say huge performance difference between MongoMK and TarMK,, that gives me very strange feeling. I do realize that tarMK sits with AEM installation and it does not need to make another call to Mongo DB for read/write operation so tarMK has slight advantage in terms of performance but huge difference does not make sense ...please elaborate if you have measured /experienced that. 

Thanks for reply.

Regards,

Chandra

joerghoh
joerghoh
Employee
October 16, 2015

Hi,

I don't have experience or exact numbers to share. I am just thinking of the latency of a network access vs the latency of a local filesystem (or even RAM if the data is cached in buffercache or mapped into RAM).

Jörg

Terms & ConditionsAccessibility statement

Loading footer...