@hrai
Please note that the topology shown in the document is just a sample architecture for the additional comments related to the load/PDFG service(for example - set up dedicated servers for specific capabilities ), quoted below.
So this setup is intended for internal users only, then a single user should also suffice (and it will save you from the overheads of handling multiple instances).
Also, for such a case, the repositories for each instance will be different and should have separate artifacts. However, there is an option to save templates/artifacts over a shared location that can be accessed from multiple instances.
So the setup topology should depend on the use-case implementation for each service and anticipated load.
We can discuss this further, please raise a request for an expert session over the admin console.
Although AEM Forms allows you to set up and run all the functionalities from a single server, you should do capacity planning, load balancing, and set up dedicated servers for specific capabilities in a production environment. For example, for an environment using the PDF Generator service to convert thousands of pages a day and multiple adaptive forms to capture data, set up separate AEM Forms servers for the PDF Generator service and adaptive forms capabilities.
thanks for your reply. Please see in-line.
>> So this setup is intended for internal users only, then a single user should also suffice (and it will save you from the overheads of handling multiple instances).
I assume you meant - single instance here?
well technically some middleware will hit the AEM Sling Servlet where OutputService/ AssemblerService will be POSTed to generate the flat PDF.
>> Also, for such a case, the repositories for each instance will be different and should have separate artifacts.
well, we only want to use PDF generation capabilities (OutputService/ AssemblerService APIs) so therefore single instance of author setup should suffice, right?
>> However, there is an option to save templates/artifacts over a shared location that can be accessed from multiple instances.
If we want to use 2 authors (for higher throughput) So in case of 2 author infront of load balancer - we may use shared datastore? is that you referred here.