I have never seen the dispatcher being used as a loadbalancer, and also I am not aware of anyone using it in this role. In 2011 someone in a project of mine tested the dispatcher as loadbalancer and connected it to 6 publish instances. It distributed the requests in a very uneven way (the first publ...

Can't you configure that already on the CI CD pipelines?    "Important metric failure behavior" in https://league.adobe.com/docs/experience-manager-cloud-manager/content/using/pipelines/production-pipelines.html?lang=en#adding-production-pipeline

I am not aware that the general AEM 6.5.x support for on-prem setups is going to be discontinued. 

If I understand the OP correct, they want to test the FILTER_PATH behavior, that the filter is invoked correctly when a matching path is provided; and that the code is not invoked when a non-matching path is provided. Your sample code hardwires that decision; if I change the FILTER_PATH parameter in...

 This parameter is used by the runtime (OSGI events) to decide if your code is going to be invoked. That means if you want to test that you have the correct parameters provided to the service you have to have a OSGI runtime running. That's rather a task for an integration test; unit tests are less s...

A scheduled job runs outside of a request context, for that reason there is no SlingHttpServletRequest available.

In the end for any production environment you need to have a supported setup; that mans that you should follow the table on the page "technical requirements", which only lists Mongo, DB2 and Oracle DB as supported to use as storage for the repository (DB2 and Oracle as restricted). That means that y...

My 2 cents: PROD and Stage are 2 different types of environments, and their role differs mostly in these aspects: A PROD environment  usually has a much higher SLA and you have monitoring and active alerting & incident handling for it. That's different from stage. When your content creation process ...

> In other words, authoring content in prod, pushing to stage for UAT, and then taking any corrections into prod and pushing down to stage?  

can you post the complete exception including the relevant parts of the stacktrace, so we can actually find out what went wrong here? the exception message alone is not enough. But also: can you please raise a feature request here and describe your usecase a bit better, especially why you want to sy...