Purpose of application gateway service

Hello, OpenMRS community,

I’m currently working on deploying the OpenMRS application on the AWS cloud. I have the openers-distro-reference application and I’m using the corresponding Dockerfiles to deploy both the backend (BE) and the new frontend (FE) within Docker containers. While I understand this process, I’m unsure about the purpose of the application gateway service.

Could someone please explain what the gateway service does and whether it’s necessary for deploying the entire infrastructure? Also, I’m wondering if it’s possible to expose the frontend app and allow it to communicate with the exposed backend app without using the gateway service.

Your help would be greatly appreciated.

Thank you.

1 Like

The gateway service is there to avoid having to deal with CORS issues, since otherwise the frontend and backend would end up being exposed on different origins. As designed, the RefApp distro won’t work without the gateway. That said, the RefApp distro can be used just as inspiration. There’s no need to deploy things the way its setup, it’s just more work on your end.

1 Like