Which option is best with AEM 6.2 between the TarMK and MongoDB | Community
Skip to main content
D
dragon2A
Level 5
October 4, 2016
Solved

Which option is best with AEM 6.2 between the TarMK and MongoDB

  • October 4, 2016
  • 6 replies
  • 4538 views

Hi Team,

I am trying to compare TarMK and MongoDb which is the best option in AEM 6.2. Someone provide the information on this. why we need to go for TarMk and why we need to go for the MongoDb.

 

Thanks in advance :) :)

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 kautuk_sahni

Hi 

Please have a look at official documentation :- https://docs.adobe.com/docs/en/aem/6-2/deploy/recommended-deploys.html

Apart form it, there is one blog post:- http://ashokkumarta.blogspot.in/2015/11/mongo-vs-tar-mk-big-debate.html

// Authoring 

 Scalability – MongoMK provides the ability to have multiple AEM instances share the same MongoDB instance. This shared all clustering approach enables horizontal scalability of AEM instances, adding additional AEM nodes as the load increases
 Replication – MongoMK reduces the overhead of replication; it effectively delegates replication functionality to the MongoDB, which has mature model to maintain replica sets. Also the no. of MongoDB replicas and AEM instances can be scaled independently
 Distributed Authoring teams – MongoMK helps when we have distributed authoring teams spread across geographies. Content changes does by all authors gets persisted to the same primary MongoDB instance and gets replicated to the secondary replica sets
 Automated Recovery – MongoDB replica sets and automated failover helps with automated system recovery when the primary MongoDB instance goes down or in case of the whole data center failure; never the less TarMK also provides the option for setting up automated recovery

The choice of MongoMK or TarMK for authoring instance can be based on no. of AEM instances required in authoring environment, in line with Adobe recomendation.
·         If more than 1 active AEM instance is needed for Authoring environment – MongoMK
·         If the volume can be handled with 1 active AEM instance - TarMK

 

Publish 

Code releases – When releasing code changes to production for Dotcom, we will have to release it to one data center, validate the release and then release it to the other data center. This is a mandatory requirement to ensure 24/7 availability. Such rolling release is well supported by TarMK. With MongoMK, code release gets replicated to all MongoDB replica’s making the isolated release to one data center difficult.
AEM Upgrades – Applying patches and release upgrades to AEM also requires rolling releases which is well supported by TarMK because of their shared nothing clustering approach
Horizontal scalability – Both TarMK and MongoMK supports horizontal scalability for publish instance. With TarMK, we can have a form of independent shared nothing AEM instances, which are kept in sync by replication.

 

The choice of MongoMK or TarMK for publish instance can be based on if the site supports user generated content or not.
·         Site support user generated content – MongoMK
·         Site does not support user generated content - TarMK 

I hope this would be of some help to you.

~kautuk

6 replies

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 5, 2016

Hi,

is there anything that in your opinion is not covered by the docs[0]?

Regards,

Opkar

[0] https://docs.adobe.com/docs/en/aem/6-2/deploy/recommended-deploys.html

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity ManagerAccepted solution
    Community Manager
    October 5, 2016

    Hi 

    Please have a look at official documentation :- https://docs.adobe.com/docs/en/aem/6-2/deploy/recommended-deploys.html

    Apart form it, there is one blog post:- http://ashokkumarta.blogspot.in/2015/11/mongo-vs-tar-mk-big-debate.html

    // Authoring 

     Scalability – MongoMK provides the ability to have multiple AEM instances share the same MongoDB instance. This shared all clustering approach enables horizontal scalability of AEM instances, adding additional AEM nodes as the load increases
     Replication – MongoMK reduces the overhead of replication; it effectively delegates replication functionality to the MongoDB, which has mature model to maintain replica sets. Also the no. of MongoDB replicas and AEM instances can be scaled independently
     Distributed Authoring teams – MongoMK helps when we have distributed authoring teams spread across geographies. Content changes does by all authors gets persisted to the same primary MongoDB instance and gets replicated to the secondary replica sets
     Automated Recovery – MongoDB replica sets and automated failover helps with automated system recovery when the primary MongoDB instance goes down or in case of the whole data center failure; never the less TarMK also provides the option for setting up automated recovery

    The choice of MongoMK or TarMK for authoring instance can be based on no. of AEM instances required in authoring environment, in line with Adobe recomendation.
    ·         If more than 1 active AEM instance is needed for Authoring environment – MongoMK
    ·         If the volume can be handled with 1 active AEM instance - TarMK

     

    Publish 

    Code releases – When releasing code changes to production for Dotcom, we will have to release it to one data center, validate the release and then release it to the other data center. This is a mandatory requirement to ensure 24/7 availability. Such rolling release is well supported by TarMK. With MongoMK, code release gets replicated to all MongoDB replica’s making the isolated release to one data center difficult.
    AEM Upgrades – Applying patches and release upgrades to AEM also requires rolling releases which is well supported by TarMK because of their shared nothing clustering approach
    Horizontal scalability – Both TarMK and MongoMK supports horizontal scalability for publish instance. With TarMK, we can have a form of independent shared nothing AEM instances, which are kept in sync by replication.

     

    The choice of MongoMK or TarMK for publish instance can be based on if the site supports user generated content or not.
    ·         Site support user generated content – MongoMK
    ·         Site does not support user generated content - TarMK 

    I hope this would be of some help to you.

    ~kautuk

    Kautuk Sahni
      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      October 5, 2016

      Adding one more reference here:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__vbf4-hi_how_to_decide.html

      ~kautuk

      Kautuk Sahni
      Ratna_Kumar
      Ratna_Kumar
      Level 10
      October 5, 2016

      //Adding with Kautuk,

      Look into this AEM GEMS session on this topic Running AEM on MongoDB: https://docs.adobe.com/ddc/en/gems/running-aem-on-mongodb.html

      Thanks,
      Ratna.

      D
      dragon2AAuthor
      Level 5
      October 5, 2016

      Thanks for the info guys. That's useful stuff. We decided to use MongoDb in authoring instance but still got doubts while posting this query on the forum. Now I got clear picture . I will keep post my experience with the MongoDB.

       

      :)

      Thejus
      Thejus
      Level 2
      December 12, 2017

      // Adding ..

      Found one more link with relevant information(Latest).

      Adobe Experience Manager - CQ Tutorials: AEM Microkernels - MongoMK vs TarMK

      Terms & ConditionsAccessibility statement

      Loading footer...