Multiple meteor apps on the same mongo db to test new releases

We’d like to release new versions of our meteor app only after having good feedbacks from a small subset of our production users.
The idea is to have two app instances (production and testing) pointing to the same mongodb under two different subdomain.
When users marked for testing connect to the production app they would be redirected to the testing one.
Is this pattern safe? are there race conditions?


In production, I am running 5 instances that all connect to the same database. I believe many who run multiple instances with Nginx load balancing use this pattern.

1 Like

I’m doing exactly that with [domain] .com and beta.[domain].com and it works great!

1 mongo db, 2 apps running on different ports and nginx for proxying according to the domain.

That’s great! thanks for sharing.