I really like the feasibility of meshIQ and the way it captures data from the middleware stack for monitoring. It’s user-friendly and customizable by business domain, which is especially helpful for industries like retail. I also think it’s a great product overall, and the 12.1 release demo I saw at a recent event really stood out to me. The plug-and-play setup made it easy to integrate with our systems and monitor our middleware effectively. We switched to meshIQ because it felt well-suited to the retail domain and because of its simplicity, and I also appreciate the security it provides. Review collected by and hosted on G2.com.
I think it could become complicated when enrollment is large. From an enrollment scalability perspective, I’m not sure how much workload it can handle or how easily it can scale as the environment grows from a business point of view. My main concern is the architecture: whether it’s designed to scale smoothly as usage increases. I’m also wondering if we can support data ingress from different platforms, not only confined to the middleware, but also from the database, so we can achieve true end-to-end scalability. Review collected by and hosted on G2.com.
Thank you for the thoughtful feedback! These are important considerations.
From an architectural standpoint, meshIQ is designed to scale and is already deployed in large enterprise environments with significant workloads. The platform supports horizontal scaling, allowing capacity to grow smoothly as enrollment and usage increase.
In addition, meshIQ is not limited to middleware. It can ingest data from multiple sources, including databases, applications, and infrastructure components, enabling true end-to-end visibility across the environment.
We typically work with customers to align architecture and sizing with expected growth to ensure long-term scalability. We would be happy to review your anticipated scale and requirements to ensure the solution is properly aligned with your business needs.
