Timeline for Benefits of Microservices processes split per kind? of process?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2022 at 14:50 | comment | added | Carlo Moretti | Hey I've been facing the same problem in my company lately and the direction I'm investigating towards is Views. Instead of talking with the actual DB which can be a single common instance, each microservice interacts with Views that reflect your ORM models and sync themselves with the underneath data for the actual DB. This way you can use ORM to couple with a View, but Views are decoupled from the underlying DB. | |
| Aug 23, 2022 at 18:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 28, 2022 at 8:23 | comment | added | John Wu | Does your DevOps team support other applications? Are they just asking you to do the same thing as everyone else? Or is this new to all of you? | |
| Apr 26, 2022 at 21:37 | comment | added | Matias | I think you nailed it in this part. Our deployment pipeline is tightly coupled to each repository using Github Actions. I am not exactly sure the motivation of the devops team to do that rather than abstracted solution from the repositories. Maybe it was just "being used to it" or not wanting to move away from it to justify the "bad move". Either way, we exposed our arguments and realized that there was no clear benefit at least in the very short term given the solutions we are building. | |
| Apr 25, 2022 at 20:19 | comment | added | Ben Cottrell | I think another issue may be having a deployment process with a dependency on the Git repository structure. I'd typically expect separate pipelines for CI and Deployment, with CI merely publishing one or more built, packaged, versioned artefacts, and a separate, independent deployment pipeline responsible for deploying whatever artefacts are necessary into an environment. If your deployment process only uses built, published artefacts rather than git repositories then the deployment pipeline should be agnostic to the source project structure in git. | |
| Apr 25, 2022 at 18:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 27, 2022 at 4:52 | comment | added | Filip Milovanović | Sounds like your DevOps team is just the "Ops" team :) If you have a separate, dedicated DevOps team that you have to engage into a power struggle with, that's in no way DevOps, despite the name. Not a super helpful comment, but puts thing into perspective. I guess you either work out your differences with the Ops team, or you present your case and convince the decision makers to let you take the ownership of the Ops part of your application for yourselves (e.g. maybe explain how going down the other path will hurt their business). Either way, there's going to be negotiation involved. | |
| Mar 26, 2022 at 17:39 | answer | added | candied_orange | timeline score: 1 | |
| Mar 26, 2022 at 17:32 | review | Close votes | |||
| Apr 10, 2022 at 3:08 | |||||
| S Mar 26, 2022 at 17:12 | review | First questions | |||
| Mar 28, 2022 at 4:20 | |||||
| S Mar 26, 2022 at 17:12 | history | asked | Matias | CC BY-SA 4.0 |