Given following microservice architecture:
Every post has a user, for which we want to have all information available.
Is more custom to:
- Have a local user cache in the posts microservice
- Make api calls to the user service on every request
- Store user information along with every post
I don't particularly like the last option when storing in the database; because of duplication, but also because it doesn't update the user data when something changes.
What is your take?