One feature that stood out for us was the query performance optimization, especially for large reporting and analytics workloads. We process high-volume financial and customer behavior data, and the platform handled complex queries much more efficiently than our previous setup.

I also appreciate the interoperability with existing tools and open formats. Our engineering team didn’t have to completely rebuild pipelines or retrain users from scratch, which made adoption smoother internally.

Another big advantage has been governance and data visibility. In a regulated fintech environment, having stronger control over data access and lineage tracking became extremely important, especially for audit and compliance requirements.

From a business perspective, watsonx.data helped reduce infrastructure inefficiencies while improving access to analytics across teams. Analysts, data engineers, and operations teams were able to work from a more unified environment instead of constantly moving data between disconnected systems. Review collected by and hosted on G2.com.

One challenge with IBM watsonx.data is that the platform can feel quite complex during the initial onboarding phase, especially for teams that are newer to lakehouse architectures or hybrid data environments. There are a lot of capabilities available, but understanding how to configure and optimize everything properly takes time.

We also experienced a steeper learning curve around setup, integration, and governance policies compared to some lighter-weight analytics platforms we evaluated. Certain workflows required more technical involvement from our data engineering team than we originally expected.

Another area that could improve is the user experience within parts of the interface. While the platform is powerful, some administrative and configuration tasks don’t always feel as intuitive or streamlined as newer cloud-native tools in the market.

Performance has generally been strong for large workloads, but during early implementation we had to spend time tuning queries and optimizing storage configurations to get consistent results across different environments.

Pricing and infrastructure planning can also become a consideration for organizations scaling large enterprise deployments. Smaller teams without dedicated data engineering resources may find adoption more challenging initially. Review collected by and hosted on G2.com.

What I like most about IBM watsonx.data is its ability to unify data from multiple sources without complex migrations or duplication, which saves time and reduces storage costs. Its open lakehouse architecture delivers strong performance for analytics, reporting, and AI workloads while remaining cost-efficient and scalable. I also appreciate the clean and organized UI/UX, which makes navigating datasets, managing workloads, and monitoring data operations more efficient for enterprise teams. The built-in governance, hybrid cloud flexibility, and smooth integrations further simplify data management and support scalable AI and analytics initiatives across environments. Review collected by and hosted on G2.com.

One area IBM watsonx.data could improve is the initial setup and configuration, which can feel complex for new users or smaller teams. Some integrations and advanced features also come with a learning curve and would benefit from clearer, more detailed documentation. In certain situations, query performance and troubleshooting can take extra effort, especially when working with very large or highly diverse data environments. Review collected by and hosted on G2.com.

What I like most about IBM watsonx.data is how it lets us query and manage data across multiple sources without needing complex data movement. Its open lakehouse architecture makes it easier to work with structured and unstructured data side by side, which has improved performance and reduced storage duplication for our analytics workloads. The integration with AI and analytics tools also helps teams process large datasets more quickly and generate insights more efficiently.

Another major advantage is its scalability and governance. The platform reliably supports high-volume enterprise data workloads while also providing strong security controls and solid data governance features. Review collected by and hosted on G2.com.

One area where IBM watsonx.data could improve is the initial setup experience and the learning curve for new users. While the platform is powerful, configuring integrations and optimizing workloads can sometimes require advanced technical knowledge, especially for teams that are new to lakehouse architectures. Clearer onboarding documentation, along with more guided setup workflows, would make adoption smoother and reduce the effort needed to get started.

I also think some UI workflows and monitoring features could be more intuitive. At times, troubleshooting performance issues or managing integrations across different environments takes extra effort than it should. Additionally, pricing and resource consumption can become expensive for large-scale deployments, so more transparent cost-optimization tools and simpler management features would help improve the overall experience. Review collected by and hosted on G2.com.

The best I love about this platform is the data security it provides by not relying on a single platform for storage. This is an extremely powerful platform with much scalable option. One more thing I love about this platform is the ability of this platform to migrate the data without much complexity when needs arises. I also love the way how the data is stored in this platform. The access control is also provided which further enhances the security of this platform.

There is also infrastructure manager in this platform which enhances visibility of the infrastructure components. It provides better understanding and effectiveness. The capability of its AI assistant in this platform is also good and can ease the task with its assistance. One best part of this platform is the IBM Ecosystem of this platform that makes this platform more robust. Review collected by and hosted on G2.com.

I love most part of this platform but I feel that the complexity of this platform is high so training from someone who had already used this platform would make the use of this platform more efficient. I also wish that this platform updates a bit more faster. Review collected by and hosted on G2.com.

I used IBM watsonx.data in several client projects over the past few months, mainly for data-heavy tasks where we needed a lakehouse-style setup. What I liked most is that it allowed us to keep data in object storage while still querying it with SQL, without needing to move everything into a traditional warehouse. This cut down on a lot of unnecessary data duplication.

The support for open formats like Iceberg was truly helpful. In one project, we had schema changes halfway through. Being able to manage versioning without disrupting existing queries saved us time. Review collected by and hosted on G2.com.

The initial setup took us some time, especially when it came to configuring storage and access controls. It’s not exactly plug-and-play, so there is a learning curve for teams new to lakehouse architectures. We also needed to review the documentation closely to understand some configuration steps. Once it was set up, it worked well. However, onboarding could definitely be smoother. Review collected by and hosted on G2.com.

I use IBM watsonx.data to centralize and manage both structured and unstructured data in a unified lakehouse for analytics and AI workloads. I like its ability to combine the flexibility of a data lake with the performance of a data warehouse in a single platform. It helps me access, process, and analyze data across hybrid environments to generate faster insights and support data-driven decisions. It also offers strong query optimization and supports open data formats, making it easy to scale analytics across hybrid environments. Additionally, it integrates well with BI tools for visualization, helping turn processed data into actionable insights. Transitioning to IBM watsonx.data helped me gain more flexibility and scalability, handle growing data volumes more efficiently while reducing costs, and support modern analytics and AI workloads. Review collected by and hosted on G2.com.

The setup and initial configuration can be a bit complex, especially for teams new to lakehouse architectures. Additionally, improving documentation, UI intuitiveness, and integration with some third-party tools would make the overall experience smoother. The initial setup was moderately complex and required some familiarity with data architecture and cloud environments. While the documentation helps, the process can be time-consuming, especially when configuring integrations and optimizing performance for specific workloads. Review collected by and hosted on G2.com.

I use IBM watsonx.data as a unified data platform to manage, access, and analyze large volumes of structured and unstructured data. I like its ability to unify data across multiple sources without requiring heavy data movement, which makes it easier to access and analyze data efficiently while maintaining performance. I also appreciate the scalability and flexibility it offers for handling large and diverse datasets. The platform supports both analytics and AI workloads in a structured way. Its data governance capabilities help ensure data reliability and security, enabling more efficient and data-driven decision-making. The initial setup was relatively smooth with proper planning and guidance, providing a structured setup process that made it easier to configure core components and connect data sources. Review collected by and hosted on G2.com.

IBM watsonx.data is a strong and scalable platform overall. Some advanced features may require initial familiarity to fully utilize, so a bit of onboarding or guidance can be helpful. Additionally, having more simplified out-of-the-box configurations for certain use cases could further enhance ease of use. Overall, these are minor areas, and the platform continues to evolve with improvements that enhance usability and performance. Review collected by and hosted on G2.com.

I like IBM watsonx.data for its ability to analyze a large scale of data and unify data from multiple sources into a single platform. It's flexible, scalable, and works well for both analytics and AI use cases. The fast delivery of queries and overall performance are impressive. It saves me time by avoiding the need to manage separate systems, making everything accessible in one place. This efficiency helps me get insights quickly. Review collected by and hosted on G2.com.

The initial setup of IBM watsonx.data was not very easy. I had to go through a lot of documentation, and setting up was moderately complex. It required some time to understand the architecture and configurations, especially during integrations. The initial learning curve is high, and it feels a bit complex initially. Review collected by and hosted on G2.com.

I like how IBM watsonx.data simplifies the process of working with distributed data, allowing me to query it in a unified way and making my workflow much smoother. I really appreciate the performance aspect, as handling large datasets feels much faster and more efficient compared to traditional data warehouse setups I've used before. The flexibility is another benefit; it works well with different data formats and integrates nicely with existing tools, so I didn't have to completely change my workflow. I find the query engine based on Presto/Trino very helpful because I can run SQL directly on data sitting in different sources without moving it first. The data virtualization capability is quite useful for creating a unified view across multiple datasets, and the open table format support, like Iceberg, is a big plus for managing large datasets reliably. The governance features also stand out, as they make managing access controls and ensuring proper data usage straightforward. Overall, these features reduce a lot of manual effort and let me focus more on building useful data models and insights rather than handling infrastructure. Review collected by and hosted on G2.com.

It's solid overall, but there are a few areas that could definitely be better. One challenge is the initial learning curve. If you're new to the ecosystem, it takes some time to understand how everything fits together, especially with concepts like data virtualization and open table formats. Performance is generally good, but for very complex queries or heavily concurrent workloads, it can sometimes need extra tuning to get the best results. It’s not always “plug and play” in those scenarios. The UI and overall user experience could also be more intuitive. Some workflows feel a bit clunky, and finding certain settings or configurations isn’t always straightforward. Integration is good, but not always seamless with every external tool—sometimes you need additional setup or workarounds depending on your stack. Lastly, documentation is decent but could be more practical and example-driven. Having more real-world use cases and clearer guides would make onboarding much smoother. Review collected by and hosted on G2.com.

I use IBM watsonx.data primarily because of its ability to provide a unified access layer to data across multiple sources without the need for heavy data movement. I like the flexibility it offers with multiple query engines, which optimizes both performance and cost for different workloads. The data virtualization feature is valuable as it allows me to access data across different sources without moving it, saving time and reducing duplication. I also find the governance and metadata management features important as they provide better control, data lineage, and trust in the data used for analytics and AI. Review collected by and hosted on G2.com.

Some areas of IBM watsonx.data could definitely be improved. The initial setup and configuration can be a bit complex, especially when integrating multiple data sources and engines. Also, performance tuning and troubleshooting can sometimes require deeper expertise, and the UI/UX isn’t always very intuitive, which makes it slightly harder for new users to get comfortable quickly. The main challenge during setup was the complexity of integrating multiple data sources and query engines— it often requires a lot of manual configuration, handling credentials, and understanding how different components interact. Getting everything (like storage, compute engines, and access policies) aligned correctly can take time, especially without clear step-by-step guidance. Review collected by and hosted on G2.com.