When doing conversion work, separate production or namespace

Question

Question

Mike Strout · Mar 13

I am starting a conversion project for a health system that is currently migrating to Health Connect. They have their DEV and TST environments in one production and their PRD in another. What is the best practice for standing up conversion environments...separate name spaces in the two productions or separate productions? Keep in mind the interfaces are temporary?

Mike

Discussion (3)3

Log in or sign up to continue

Jeffrey Drumm · Mar 13

While you can create multiple productions in a single namespace, you can only run one at a time. There's really no good reason to have more than one production in a namespace ... and with each production in its own namespace, they can be running concurrently.

2 0

score 0 · Answer 1 · 2025-03-20T10:07:43-04:00

Mike Strout · Mar 20

Thank for weighing in on this. This makes total sense.

0 0

score 4 · Answer 2 · 2025-03-14T02:41:46-04:00

Well, I highly recommend to you to not use the same instance of Health Connect for TEST, DEV and PRODUCTION, even more, I recommend to you to deploy each environmnent in different servers.

It won't be the first time that a code un DEV has a infinite loop creating heavy globals that use all the space in the disk.