1. What are the two main categories of metric provided by Vitals?
Vitals is a plugin for Kong that provides monitoring and analytics capabilities. The two main categories of metric provided by Vitals are:
System metrics: These are metrics related to the underlying system on which Kong is running, such as CPU usage, memory usage, and network activity. These metrics are used to monitor the health and performance of the system and to detect any potential issues or bottlenecks.
Kong-specific metrics: These are metrics related to the Kong API Gateway itself, such as the number of requests processed, the latency of requests, and the status of plugins. These metrics provide insight into the performance and usage of Kong and can be used to optimize the gateway for specific workloads or to troubleshoot issues that may arise.
2. Which is the method for load balancing in Kong?
Kong provides several load balancing methods, including:
Round-robin: In this method, requests are distributed evenly among the available upstream servers in a sequential manner.
Least connections: In this method, requests are sent to the upstream server with the least number of active connections.
IP Hash: In this method, requests are sent to the same upstream server based on the client's IP address. This can be useful for maintaining session affinity.
Consistent Hash: In this method, requests are distributed based on a consistent hash algorithm, which allows for better cache utilization and improved resilience to upstream server failures.
Random: In this method, requests are distributed randomly among the available upstream servers.
3. What are the components of Kong Konnect?
Kong Konnect is a cloud-native service connectivity platform that provides several components, including:
Kong Gateway: This is a highly performant, cloud-native API gateway that provides traffic management, security, and observability features.
Kong Studio: This is a collaborative, web-based IDE for designing, testing, and publishing APIs. It includes a visual editor for OpenAPI and GraphQL schemas, a built-in mock server for testing, and integration with Kong Gateway for publishing.
Kong Immunity: This is a cloud-native, AI-driven security solution that provides protection against OWASP Top 10 threats, including SQL injection, cross-site scripting (XSS), and more.
Kong Vitals: This is a real-time API analytics and observability solution that provides insights into API traffic, performance, and errors.
Kong Dev Portal: This is a customizable developer portal that provides API documentation, code samples, and other resources for API consumers.
Kong Manager: This is a centralized management console for administering Kong Konnect components, including Kong Gateway, Kong Studio, Kong Immunity, Kong Vitals, and Kong Dev Portal.
4. Every application service to be managed through Konnect Runtime needs to be represented by a Konnect Service in Service Hub. Is it correct statement?
The statement "Every application service to be managed through Konnect Runtime needs to be represented by a Konnect Service in Service Hub" is true.
5. Konnect services can have multiple versions active simultaneously. Is it correct statement?
Yes, that statement is true. Konnect Services in Service Hub can have multiple versions active simultaneously, which enables teams to deploy and manage new versions of an application service without affecting the existing versions that are currently serving production traffic. This also allows for A/B testing, blue-green deployment, and gradual rollout strategies. Each version of a Konnect Service is represented by a unique version identifier, and traffic can be routed to specific versions of a Konnect Service based on routing rules and traffic splitting configurations.
No comments:
Post a Comment