I think it's too easy to be sucked in by the promise of distributed X or eventually consistent Y.

In the past I managed migration of a few services away from Hazelcast as the team started peeling away the nice abstractions they'd become used to so they could handle things they hoped it would protect them from. All of a sudden a distributed lock isn't a lock if your cluster splits.

In the end almost everything ended up back in Postgres. Resistance was surprising - there was a lot of opposition to simple things due to a fear that the database would be harmed by being used to hold a few row locks, for example.

I can see why people overlook the obvious when the complicated solutions seem more sophisticated, which is easy to mistake for "better".