New answers tagged

1

This kind of issue is common in distributed systems. The simplest solution is to combine the check for whether a change is allowed with the request to make the change. This technique is useful in a number of contexts. For example, let's forget the loan for a second and just focus on the credit card. Let's say you have a table that contains active credit ...


1

Given that the algorithm for vector clocks is defined such that any process increases one of the values in the vector it should be impossible for any two distinct VC to have the same value. However, there is obviously the trival case of comparing a message with itself, when you would of course expect the VC to be equal as they are duplicates of each other. ...


2

I think you said it in your first sentence - the solution is made more complex when you have intertwined or distributed validation logic. My first step would be to refactor the validation logic into a customer validation service (for lack of better words). Most countries have rating services of sort, companies have internal blacklists and customer ...


Top 50 recent answers are included