Vertica Review
Anonymous | TrustRadius Reviewer
December 14, 2019

Vertica Review

Score 7 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Vertica

Vertica forms the analytics database that takes in realtime streaming data (from Apache Kafka) and is used to provide customer insights in near real-time. It is used for the consumer-facing web portal and mobile applications.
  • It is able to intake real-time streaming data without much pre-processing and latency.
  • Easy to integrate with real-time streaming ingestion engine.
  • Vertica does not perform well when you have a lot of schemata.
  • The management console including GUI is lacking features and can be improved with features that are typical of a database.
  • Positive impact on ROI by being able to get customer insights in real-time.
  • Positive ROI through reduced time to set-up and maintain Vertica instances.
SAP HANA, Oracle, MySQL, and PostgreSQL are too heavyweight for achieving real-time latency requirements. Google BigQuery is limited to Cloud that makes hard to integrate with a large ingestion pipeline that may have both Cloud-based and on-prem components. Hadoop is much more complex to setup. Snowflake is again Cloud-based and is a new player so its reputation is not well known.
HP/Micro Focus Vertica support is in par with other bigger vendors. In addition to this, there is enough best practices documentation available for some of the most common ways you will use Vertica that makes it easy to get Vertica up and running.

Do you think Vertica delivers good value for the price?

Yes

Are you happy with Vertica's feature set?

No

Did Vertica live up to sales and marketing promises?

Yes

Did implementation of Vertica go as expected?

Yes

Would you buy Vertica again?

Yes

Vertica is well suited when latency from incoming data is key and you need Strickland timing guarantees to process the real-time streaming data. It is very well suited if you are using Confluent/Apache Kafka as the set-up and install is super easy and there best practice documentation available for it. It is less appropriate where you are looking at complex queries and schemas.