What makes a good microservice framework?

What makes a microservice framework is an incredibly good question and one that is open to a multitude of opinions. In an attempt to remove the subjectivity, we will break down the features of a good framework and try to allocate a score for each of these functions in a consistent way. The following diagram is a hierarchical mind map of the features that I deem necessary. When you are assessing the framework that is the best for you and your project, you can use this framework, adding or removing any of the attributes that may be relevant:

Here are some of the features you need to keep in mind while choosing a good framework:

• Ability to interface with other frameworks: It must be possible to interact with any service built with the framework by clients who are not built using the same framework:
  • Implement standards: A standard message protocol should be used to maximize interaction, for example:
    • JSON-RPC
    • Thrift
    • Protocol Buffers
    • JSON
  • Open: The framework...