Quantcast
Channel: Comments on: CQRS isn’t the answer – it’s just one of the questions
Viewing all articles
Browse latest Browse all 24

By: Matt S.

$
0
0

I’m still having a hard time wrapping my brain around this technique when it comes to my users’ (primarily website users) need for instant gratification.

They expect to see their recent edits applied. I previously commented about a system that allows its users to update their account information. If they make such an edit, realize they forgot something, then go back to the edit view/page to change what they forgot, they may still see the old information (prior to their edit moments ago).

I would really rather not have to code for an ambitious user that constantly checks to make sure the change they just made is taking, and reissuing it if not (i.e. view edit page, submit change, view edit page and still see old data, submit change again, view edit page, submit change again, …).

Am I missing something or are we only talking about the customer service representative example I keep seeing replayed?


Viewing all articles
Browse latest Browse all 24

Latest Images

Trending Articles





Latest Images