There are a number of areas where Kong Kuma can improve. One is in terms of product delivery, such as Helm charts. There are a lot of gaps in the Helm charts currently. Another is in terms of the default monitoring and logging setup. It is not as production-ready as it could be. By default, Kuma comes with Loki, Yagger, and Prometheus to monitor the control plane and data plane, but the unified dashboarding and logging solution should be closer to production-grade. It is good for trying out the product, but I would not recommend taking it to production without setting up your own monitoring and logging solution. Additionally, Kuma recently released Fivecarless Mesh, which was built on top of Envoy. The challenge with this is that it adds overhead. If you want to run 100 containers in production, you will actually need to run 200 containers because you need to run one sidecar container per pod. Overall, I think Kong Kuma is a moderate product, but I would not personally recommend it for production use.
Service Mesh is a dedicated infrastructure layer for handling service-to-service communication across microservices, providing observable and manageable connections for complex applications.
Used primarily in cloud-native environments, Service Meshes enhance microservice architectures by managing traffic, ensuring security, and monitoring operations. With features for load balancing, health checking, and traffic management, they allow teams to focus on developing features rather than...
There are a number of areas where Kong Kuma can improve. One is in terms of product delivery, such as Helm charts. There are a lot of gaps in the Helm charts currently. Another is in terms of the default monitoring and logging setup. It is not as production-ready as it could be. By default, Kuma comes with Loki, Yagger, and Prometheus to monitor the control plane and data plane, but the unified dashboarding and logging solution should be closer to production-grade. It is good for trying out the product, but I would not recommend taking it to production without setting up your own monitoring and logging solution. Additionally, Kuma recently released Fivecarless Mesh, which was built on top of Envoy. The challenge with this is that it adds overhead. If you want to run 100 containers in production, you will actually need to run 200 containers because you need to run one sidecar container per pod. Overall, I think Kong Kuma is a moderate product, but I would not personally recommend it for production use.