Timeline for Microservices: separate db instance vs. separate db server
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5 at 17:40 | vote | accept | weno | ||
| Dec 15, 2023 at 16:57 | comment | added | JimmyJames | @Flater That's pretty much what I am saying. As long as you keep a strict separation between these dbs, you can always split them out later when/if you know you need to. The biggest risk with this, IMO, is that some engineer or dev comes along that didn't get the memo or doesn't understand the goal and does something 'clever' that couples the dbs. | |
| Dec 14, 2023 at 22:21 | comment | added | Flater | The issue can be significantly mitigated if the company agrees to at least be willing to separate the db if and when it turns out that there is a divergence in needed database versions. The more flexible you are at handling this if it happens in the future, the less you need to pre-emptively prepare for it. | |
| Dec 14, 2023 at 15:07 | history | edited | JimmyJames | CC BY-SA 4.0 |
added 8 characters in body
|
| Dec 13, 2023 at 20:52 | history | edited | JimmyJames | CC BY-SA 4.0 |
added 1 character in body
|
| Dec 13, 2023 at 18:50 | history | answered | JimmyJames | CC BY-SA 4.0 |