Timeline for Possible Solutions for avoiding applications sharing database
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 22, 2024 at 20:38 | comment | added | Juan Carlos Eduardo Romaina Ac | The comment was towards how the OP explained the scenario. I agree with your ideas. | |
| Mar 6, 2024 at 1:06 | comment | added | Flater | Plainly put, if you need to keep all usages of your "package" in sync between services, that makes it a service of its own. But if your services can happily use their own version of the package for their own reasons, then the monorepo is not problematic even if in a microservice architecture. | |
| Mar 6, 2024 at 1:05 | comment | added | Flater | W.r.t. the second to last bullet point, "monorepo" and "monolith" operate on two different levels. One focuses on the codebase organization whereas the other focuses on runtime separation (or lack thereof). One does not automatically mean the other. Monorepos can be used by microservices, as long as the shared projects between services do not automatically force you to update the service. This is similar to the way Nuget/npm packages are intended to work: making newer versions available does not force the consumers of your package to immediately upgrade to that newer version. | |
| Mar 5, 2024 at 22:50 | history | answered | Juan Carlos Eduardo Romaina Ac | CC BY-SA 4.0 |