I think the two main reasons for the microservice flag are scaling (Create a "search" service which can be scaled separatly instead of scaling the whole application) and avoiding implementations that have to be refactored later when implementing the microservices. Those reasons are pretty valid from my point of view so #NoOffence.

Beside that I do not see any other valid reasons why this has not been implemented yet, because I guess that the implementation itself should be quite easy. - Do you know some?
Actually I've already scanned the whole blockchain some weeks ago using my Java-API to collect usernames and their IDs - It was done in about 2 days consuming about 2GB of RAM so the resources should not be a problem at all. We also would only need to save the metrics (like number of votes, number of characters, ...) for each post and not the whole content of it - This saves a lot of disk space. Also projects like SteemDB have shown that it is not that hard to scan the blockchain and store the data.