Likelihood to Recommend kdb is well suited for real time tick data and time series analytics.
Read full review Presto is for interactive simple queries, where
Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like
Vertica Read full review Pros Time series analysis. The built-in vector operations are extremely fast. Also with the q language you can code up any customized analytical ideas quickly. The database are all file based, very easy to maintain. Very solid and fast interface to websocket, so you can interface with javascript easily. Read full review Linking, embedding links and adding images is easy enough. Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope). Organizing & design is fairly simple with click & drag parameters. Read full review Cons Run time error message readability, particularly for new users. Backwards compatibility between versions. Read full review Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem. Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override. UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc. Read full review Likelihood to Renew switching costs
Read full review Usability its ok
Read full review Support Rating We don't use it.
Read full review Alternatives Considered Python is very commonly used for large data analysis and in general is much easier to pickup than kdb+. The biggest drawback of kdb+ is the learning curve.
Read full review Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
Read full review Return on Investment It perfectly solves most of our real time tick data needs. Finding good kdb resources is slightly difficult. Also new people trying to learn kdb experience a relatively longer learning curve. Read full review Presto has helped scale Uber's interactive data needs. We have migrated a lot out of proprietary tech like Vertica. Presto has helped build data driven applications on its stack than maintain a separate online/offline stack. Presto has helped us build data exploration tools by leveraging it's power of interactive and is immensely valuable for data scientists. Read full review ScreenShots