I primarily use Gloo Platform to manage APIs and implement API Gateway capabilities, control traffic routing, and improve observability across Kubernetes applications. These are the main use cases for this platform. I have used Gloo Platform to manage public Kubernetes APIs in a cloud platform. In our project, we use real-time APIs to the public cloud APIs. Regarding control traffic routing, whenever any of our applications are managed in the API CRD, we control and manage the inbound and outbound data routing traffic. We can see our application's inbound and outbound data through this platform, making it very useful.
Gloo Platform provides numerous features including mesh and gateways, and I primarily use the gateway feature, with occasional use of the mesh feature for specific components. The gateway feature manages all APIs, API endpoints, and different services running in my application, providing features such as rate limiting, observability, and visibility into all incoming traffic. Gloo Platform's gateway feature is what I appreciate most, and I occasionally use the service mesh because it is based on Istio itself, depending on requirements. I mostly use the mTLS feature of the service mesh. Gloo Platform's features are optimal for my use case because I have numerous applications and microservices running, requiring rate limiting and traffic management integrated into one platform, which proves very beneficial.
We have many microservices written in Glue, which trigger based on certain events. The Glue service is responsible for containerizing and running them over the cloud. We use Glue for various purposes, including data computing.
Gloo Platform is a versatile API and microservices management tool known for its robust security, seamless integration, and advanced traffic handling capabilities. It effectively bolsters organizational efficiency by improving workflows and reducing manual tasks through automation. Users value its support for multiple languages, comprehensive analytics, and its ability to enhance service mesh implementations for better network management.
I primarily use Gloo Platform to manage APIs and implement API Gateway capabilities, control traffic routing, and improve observability across Kubernetes applications. These are the main use cases for this platform. I have used Gloo Platform to manage public Kubernetes APIs in a cloud platform. In our project, we use real-time APIs to the public cloud APIs. Regarding control traffic routing, whenever any of our applications are managed in the API CRD, we control and manage the inbound and outbound data routing traffic. We can see our application's inbound and outbound data through this platform, making it very useful.
Gloo Platform provides numerous features including mesh and gateways, and I primarily use the gateway feature, with occasional use of the mesh feature for specific components. The gateway feature manages all APIs, API endpoints, and different services running in my application, providing features such as rate limiting, observability, and visibility into all incoming traffic. Gloo Platform's gateway feature is what I appreciate most, and I occasionally use the service mesh because it is based on Istio itself, depending on requirements. I mostly use the mTLS feature of the service mesh. Gloo Platform's features are optimal for my use case because I have numerous applications and microservices running, requiring rate limiting and traffic management integrated into one platform, which proves very beneficial.
We have many microservices written in Glue, which trigger based on certain events. The Glue service is responsible for containerizing and running them over the cloud. We use Glue for various purposes, including data computing.