How many public clouds are you currently using?
01%
125%
244%
320%
46%
Greater than 41%
Content you might like
How would you prioritize adding native vector search capabilities directly to core MySQL storage engines (e.g., InnoDB)?
Note: This poll is specifically about vector search as a general-purpose feature in the core database, separate from specialized analytics engines like MySQL HeatWave.
High Priority: This is a critical need. We want to run AI/vector workloads on our primary transactional data without relying on a separate database or a specialized analytics add-on.
Medium Priority: This would be a valuable feature for future projects. It would allow us to innovate on our core database, but it's not an immediate requirement.75%
Low Priority: This is a nice-to-have, but not essential. Our primary focus for MySQL remains on its traditional OLTP performance and stability.
Not a Priority: This is not a good fit for MySQL. We believe vector workloads are fundamentally different and are best handled by a dedicated system, keeping our core MySQL lean.25%
Unsure / Need More Information: We are not yet clear on the performance, security, or operational impact of integrating this capability into our core transactional engine.
Which key pentesting capability do current AI-driven vendor solutions most fail to cover?
Do you have the visibility you need across your VMs, containers, and multi-tier app stacks in order to achieve your DevOps and automation goals?
Yes80%
No15%
I'm not sure4%
