Monoliths are solution in search of problems.
Micro services are solution in search of problems.
Generally, focus on solving the problems first.
Can the problem be solved by some static rendering of data? Monolith is better solution.
Does the problem require constant data updates from many sources and dynamic rendering of data changes?
Micro services and reactive architecture are better solutions.
There’s no one size fits all solution. The better software engineers recognizes the pros and cons of many architecture patterns and mix match portions that make sense for the solution, given schedule, engineering resources, and budget.
I don't understand what you mean by "static rendering" vs "dynamic rendering", but I suspect I wouldn't agree on that.
Monolith vs microservice IMO depends more on team size/structure, stage of the project (POC/beta/stable/etc.), how well defined the specs are, … Rather than the nature of the problem itself.
Generally, focus on solving the problems first.
Can the problem be solved by some static rendering of data? Monolith is better solution.
Does the problem require constant data updates from many sources and dynamic rendering of data changes? Micro services and reactive architecture are better solutions.
There’s no one size fits all solution. The better software engineers recognizes the pros and cons of many architecture patterns and mix match portions that make sense for the solution, given schedule, engineering resources, and budget.