I think it is a project focus on Microservice Ecosystem. And because it is not only a rpc framework but also a microservice platform. It can solve all issues from different industries. But I think he/she means it is good at solving those several industries. Such as, 'SET MODULE' feature for quick deployment for Gaming, and I can see TARS is also a mature project using in Akraino Community in Linux Foudation Edge Computing, and I can also see there is a speech name "TARS for FinTech" in FinTech Foturm at New York. So, maybe the concept of TARS is "Let developers focus on developing their business logic ONLY."
The data in those tables should be presented using charts to make it easier to eyeball comparisons. Tables full of numbers are much less intuitive than a nice upward curve.
When evaluating an RPC mechanism I'm mostly interested in performance benchmarks between existing protocols and discussion of schema migration/mutation than architecture (if I'm using your software as a dependency, don't tell me how it works, show me the API and benchmarks!).
There appears to be a benchmark table in docs/performance.md but I hope some native speaker can translate for the English speaking folks among us.