FAQ

Question: What is service mesh?

Answer: A service mesh is a way to control how different parts of an application share data with one another. Unlike other systems for managing this communication, a service mesh is a dedicated infrastructure layer built right into an app. This visible infrastructure layer can document how well (or not) different parts of an app interact, so it becomes easier to optimize communication and avoid downtime as an app grows.

Question: What is Meshery?

Answer: Meshery is the open source, service mesh management plane that enables the adoption, operation, and management of any service mesh and their workloads.

Question: Why was Meshery created?

Answer: As an open source, vendor neutral project, Meshery was created out of the necessity to enable service mesh adopters to overcome the challenge of complex virtual networking; to come to expect more from their infrastructure; to enable the world to understand and operate any service mesh with confidence.

Question: What does Meshery do?

Answer:

  • Operates service meshes with confidence,
    • with operational best practices.
  • Compare apples-to-apples performance across service meshes.
  • Understand behavioral differences between service meshes.
  • Track your application performance from version to version.

Question: What is mesheryctl?

Answer: A command line interface to manage Meshery.

Question: How to install Meshery?

Answer: Meshery runs on a number of platforms. Popular Installers:

Question: What is the difference between make run-local and mesheryctl system start? Do they both run Meshery on my local machine?

Answer: Yes, both of them do run Meshery on your local machine. make run local builds Meshery from source and runs it on your local OS, while mesheryctl system start runs Meshery as a set of containers in Docker or in Kubernetes on your local machine.


Don't find an answer to your question here? Ask on the service mesh discussion forum.