Hi, I'm going to work on $subject. Currently, AF manage registry resources (external apis, properties, api keys) using Stratos managers, generally it is not a responsibility of SM, and with the docker support in next release we will have 1 Stratos instance, so we are integrating Greg to manage resources in AF.
Right now, We have 3 Stratos Managers for Dev, Test, Prod environments and we have mounted App Server registries to SMs and then all 3 registries to App Factory as shown in the Diagram 1. With this configuration, to save registry resources, we do remote call to SM and we read resources directly from AF registry (which improves the performance of page loading in Runtime Config page). *Diagram 1* *We are planning to:* 1. Add 3 Greg instances to manage registry resources for each environment and mount App Server registries. 2. With the improvement, we have discussed here "[Architecture] [AF] Removing Registry Mounts for the Dev, Test, Prod Registries", there will not be registry mounts with AF, which improves performance of loading tenant, tenant registry and artifact, etc.... When saving registry resources, we do remote call to Greg as earlier, and keep only the name and description of each resource in afdb.AF_RESOURCE table. When loading the Runtime Config page we get data from afdb and display to the user. To see more details of the resource, there's a button in front of each resource to load all resource information from Greg and display. 3. Save registry resources in config registry to give more security. (Currently, we save registry resources in governance registry, so it's accessible to any carbon server (AS, ESB, etc...)) Diagram 2 shows how AF will be with the above improvements. *Diagram 2* Thanks Amalka
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
