So I’m architecting a small system, where there will be 2 apps. One that is end-user facing only (public like app) and another that is admin only. The public one will be connected to a database containing pruned and cleaned up records while the admin one will be connected to both that database and another one. Now I would like that the admin app would be connected to the public facing one, able to use Erlang node comm, but not the other way around, so that the admin app could directly change state in the public one. This will be deployed in AWS EC2, I will open the node communication ports in the public one restricting the ip range to that of the admin one.

The reason for this is that the public facing app will contain views based on data from the pruned datasets, but the admins will be doing updates to the data monthly, so I want to re-use the views from the public facing app to output “previews” in the admin with data that hasn’t been yet persisted, to see if everything adds up correctly, this way preventing duplication of views. Does this seem like a reasonable idea? In my head it does.

If that is possible, how would I set up the cookies and node names and connect the admin app when it starts up?
The idea is that in case I end up with several public facing instances in the future, I would be able to retrieve their addresses registered in the loadbalancer and then automatically connect the admin to any N public apps.

Thanks for any insights