Expandir minha barra de realizações na Comunidade.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.

SOLUCIONADO

Author Instances in Parallel

Avatar

Level 6

Hi,

I know that from AEM 6.0 clustering is only possible via MongoMK.

I'd like to have two or more author instances working in parallel, but I don't like to add MongoDB in the Stack.

Is there any way to have multiple author instances working concurrently be kept in sync?

Thanks

1 Solução aceita

Avatar

Resposta correta de
Level 8

Without MongoDB and clustering there are a lot of good options to have two author instances which operate in parallel.

In 6.0 you can still run CRX2 and you could do the old style clustering. The big down side is that you won't have an upgrade path - in 6.1 CRX2 support is no longer available. 

You can use job off loading to move workflow processing or other job based processes to run on another author which removes load. You still have to do your authoring on one instance but if you have lots of image rendition creation work or other batch processing it can help. 

The only other viable solution is some sort of sharding where you edit half your content in Author 1 and the other half in author 2. That's problematic however because it is really difficult to enforce systematically and its easy end up with overwrites and conflicts. It would stay away from a scenario like that. 

If you have a situation where you really legitimately requires an active - active scenario you need to take another look at MongoMK - its the only good solution in my opinion. 

Ver solução na publicação original

3 Respostas

Avatar

Resposta correta de
Level 8

Without MongoDB and clustering there are a lot of good options to have two author instances which operate in parallel.

In 6.0 you can still run CRX2 and you could do the old style clustering. The big down side is that you won't have an upgrade path - in 6.1 CRX2 support is no longer available. 

You can use job off loading to move workflow processing or other job based processes to run on another author which removes load. You still have to do your authoring on one instance but if you have lots of image rendition creation work or other batch processing it can help. 

The only other viable solution is some sort of sharding where you edit half your content in Author 1 and the other half in author 2. That's problematic however because it is really difficult to enforce systematically and its easy end up with overwrites and conflicts. It would stay away from a scenario like that. 

If you have a situation where you really legitimately requires an active - active scenario you need to take another look at MongoMK - its the only good solution in my opinion. 

Avatar

Level 6

Hi orotas,

thanks for your reply.

In case I go with mongDB on author. Can I have the publish servers running on TarMK?

Thanks

Avatar

Level 8

Yes that is fairly standard practice - you can use TarMK for publishers and MongoMK for author without any issues.