> Personally I think the "truth" lies in between. Bigger services that cover key functional areas.
This. What the GP was talking about is something like nano-services. Who really writes a whole service stack for every function?
In addition to functional areas, I also like a service when a single job needs to get done. For example, read message from queue, do some processing, put result somewhere. The beauty of the service here is I can write it once, test it, deploy and it just works. I don't have to worry about it randomly getting broken from code changes in a larger monolith.
And in your case I don't know what you can't get the line number and stack trace from a microservice. Likewise you can get tracing between microservices using something like Zipkin.
Personally I think the "truth" lies in between. Bigger services that cover key functional areas.