If forced to make infrastructure budget cuts in 2023, what areas would you cut?
Hardware31%
Software58%
Network44%
Storage30%
Communications11%
Cloud5%
Sort by:
Content you might like
Yes, going with a best of breed model - multi-vendor27%
Yes, going with a single vendor SASE model44%
Learning/Planning Phase9%
No.18%
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.7%
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.73%
Low Priority: This is a nice-to-have, but not essential. Our primary focus for MySQL remains on its traditional OLTP performance and stability.7%
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.13%
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.
It might be interesting to ask which categories get how much of a cut
If the target is a 10% overall reduction, what percentage to each category. Unfortunately for us, we had a people category too. And since we constantly squeeze all the non-people categories all the time a 10% budget cut typically would impact people the most. This is probably a big corporate “norm” but always was very painful in my experience