Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Yes, I'm aware that there are organizational measurements as well to be taken. However, the question is already broad enough (as others have already pointed out) and I even think most organizational matters would be off topic here. Hence, I want them to be excluded here. Thanks nevertheless for your thoughts! Commented Sep 21, 2023 at 8:01
  • 1
    @cis: well, my point is that it makes not much sense to seek for technical measures by ignoring the organizational aspects and quality requirements. Those things typically go hand-in-hand, and any sensible approach should never ignore this. Commented Sep 21, 2023 at 8:04
  • Yes, I agree, you need to consider all aspects in the end. But, again, I think that discussion might be too broad for this site. I made an edit to my answer. Hope that makes it clearer what I'm asking for here. Commented Sep 21, 2023 at 8:30
  • 3
    "you can't tech your way out of a people problem" +1 Commented Sep 21, 2023 at 15:11
  • "sync the fields automatically (and only automatically!) from the former information." - depending on the subsystem, this may involve manual steps, and there might be (non-automatic) two-way synchronisation. Granted, you'd likely have two fields in the secondary service, like true_suitableFor… and divergentLocal_suitableFor…, where the former is always, automatically, immediately synced from the source of truth, and the latter is the value that the service is using internally. That way, you can find and deal with the inconsistency in a single database at least. Commented Sep 21, 2023 at 16:05