architecture - Use different ID's ranges for dev and prod databases -
I am working together on a web service with a large number of integration tasks. We connect our services to tens of other services, each of which has its own reserves. Of course, we have some different environments for God, stage and production purposes. Each integrated service has at least two environments: Dev and Prod. I firmly consider two approaches to isolating the environment:
First, two different DB for another
The second is to use reserved categories for the primary key of the three different DB and used items for integration (such as user PK, no order, etc.) In this case, we restrict entry to unstable phase env from DB stage only and prevent any conflicts from reserved categories.
But the idea of using reserved categories or ID seems strange to me, any advice?
UPD: Let me clarify my position in some other way. For each third party service environment, there are two environments in my favor: platform and production, if I have my separate database and without any specific point of points, there are separate databases which are on my side If the third party is transmitted in service, then there will be conflict between my platform and the third party service parties. Should I use a DB for Stage and Prode environment or apply the limitations of the ID?
And prod in the same database?
This state holds and is physically separated.
If nothing else, then how else do you allow new database changes to be verified in the forum (without trial)?
Comments
Post a Comment