Choosing a Write Pattern for Three Different Data Types

A social app has three kinds of writes: (a) a "like" counter on posts, incremented millions of times a day; (b) a user's profile bio, edited rarely but read constantly, where the user must see their own edit immediately; (c) raw analytics events, written once and almost never read individually (only aggregated in batch later).

For each of (a), (b), (c):

1. Recommend a write pattern (write-through, write-back, or write-around) and justify it.
2. State the main risk of your recommendation and how you would mitigate it.