2 years ago
Hi! I am just curious about what App Sleeping should and shouldn't be used for.For example, the Chatwoot template has in-built datastores (Redis & Postgres), is it fine to enable App Sleeping for them? Are there any known restrictions? I could potentially see it causing unintended side effects (and at the very least creating a waterfall of wake calls between the user-facing instance & the datastores, making cold start latency worse).Thanks :)
1 Replies
2 years ago
When Railway sleeps an app it gets sent sigterm, I know postgres then can shut down safely, so data loss wise you should be fine, can't see redis not being able to shut down safely as well.
And you can wake a service via the private network, so there's no issues there either.
Chatwoot may or may not keep a constant connection open to the databases so that may outright prevent them from sleeping.
As for waking the databases, as long as Chatwoot can wait for the cold start or attempt connection retrys then that would also work.
But ultimately, you won't know until you try, though probably best to test on a test deploy of the Chatwoot template.
