@AEMWizard Indexing would help in improving search performance, Probably load balancing strategies on publishers is an option as in your design it consistently hits the publish instances for each search result and can not be cached. 

@Kiranchonkar It could be due to firewall settings and the path might be blocked or related to maven version. https://backstage.forgerock.com/knowledge/kb/article/a15127846  

@neeraj_24412 Can you check the logs on the publisher, could be a permission-related issue for the user.

@Ankan_Ghosh Not sure of the issue here, but you could probably make use of groovy scripting to update it for all pages.

@aniketp1012 Currently I don't have a sample,however, you can check this https://github.com/arunpatidar02/AdaptTo2019 shared earlier for a similar query.  

@aniketp1012  The SPA Editor is an AEM-provided solution for React and Angular applications to integrate directly with AEM with in-context editing. This is typically used when,  you plan to write your entire frontend site in React or Angularyou require SPA-controlled routing and want to serve SPA we...

@arvind There is no fixed architecture for this, it usually depends on many factors.   However, there would be a minimum of 1 Author Instance, 1 Publish instance, 1 Dispatcher, and 1 Load Balancer. And on production- Usually, there are multiple publish instances and dispatchers to allow for redundan...

@Steve_A1 contexthub is OOTB for personalisation- https://medium.com/@manumathew28.94/contexthub-in-aem-for-personalization-52b888511bf  

@NaveenT1 Yes you will have to update to the latest version, it seems its an issue with 2022.10.9145.20221006T013555Z-220800, I tried in 2023 versions, and it was working fine- 2023.1.10675.20230113T110236Z-220900. You can download the latest SDKs on your local.

@NaveenT1 probably you might need the latest service packs, looks like the error is related to coral js.