rtagns limitation

[vahid yg]

I'm using Tinode as a standalone chat service alongside my microservices. I also use auth-rest for authentication. However, there's a problem: when Tinode starts up, it checks the /rtagns route, and if my server doesn't respond, Tinode crashes. This behavior goes against the principle of decoupling services.

Is there a way to prevent Tinode from calling the /rtagns route at startup, or is there another recommended approach to address this issue?

[Gene]

On Monday, December 23, 2024 at 3:12:16 PM UTC+3 vahid yg wrote:

I'm using Tinode as a standalone chat service alongside my microservices. I also use auth-rest for authentication. However, there's a problem: when Tinode starts up, it checks the /rtagns route, and if my server doesn't respond, Tinode crashes. This behavior goes against the principle of decoupling services.

We never made a promise for Tinode to be a microservice. For example, Tinode would not start if the database is not available.

 

I see why it might be useful to retry the rest_auth service if it's not available on startup, but it's not a simple fix.

 

Is there a way to prevent Tinode from calling the /rtagns route at startup, or is there another recommended approach to address this issue?

Start rest_auth first. Or use other means to restart Tinode, like docker-compose. 

 

[Gene]

On Monday, December 23, 2024 at 3:12:16 PM UTC+3 vahid yg wrote:

I'm using Tinode as a standalone chat service alongside my microservices. I also use auth-rest for authentication. However, there's a problem: when Tinode starts up, it checks the /rtagns route, and if my server doesn't respond, Tinode crashes

BTW, it does not crash. There is a difference between a crash and a shutdown when an expected condition is not met.