Cache-Aside is an Antipattern. It forces you to define your caching logic at the application layer, and suddenly the app must care about--and actually implement--your caching strategy. This is very difficult to scale correctly and is a common source of stale data and race conditions.<p>Better to treat caching as part of your overall database infrastructure. If caching "hot" data is really important for your app, make sure your data layer supports read-through and write-through caching. Or use the "CQRS" Pattern and read from a different source than your writes (allowing your writes to transparently apply whatever underlying caching strategy you need to support the reads).<p>The MSDN article on CQRS actually has some good advice on combining it with Materialized Views and handling consistency issues. Worth reading if you're interested in solving your caching problems.
What CQRS, an index table or simply "retry" (is this even a "pattern"?) has to do with "the cloud"?<p>Don't get me wrong, I think is a lovely page (bookmarked), but I fail to see how those techniques are necessarily tied to the cloud.<p>One thing is to put our services in the cloud, another is to put our concepts in it.
What's going on over at microsoft? They've had a flurry of OSS announcements, a linux-for-switches fork, are posting relevant tech articles etc. This isn't the same microsoft I know. Is there some sort of change in the direction of leadership? I haven't seen any articles about changes in strategy in these directions but am seeing a lot of activity.
Interesting read. Although, I wasn't a fan of the banner asking for feedback at the bottom. I immediately clicked no without reading what it was (It was something to the extent of 'Is this page helpful?') Although, after dismissing it I wanted to say Yes but after submit I can't change my opinion.